NetXMS Support Forum

Vozmozno ne obnovilis' dannie esche. Versija obnovitsja posle configuration poll.

Hi!

Looks like a bug. I was able to reproduce this on my system, so hopefully I'll come out with solution soon.

Best regards,
Victor

That's very strange that cluster nodes does not appear under "entire network". How do you have cluster object configured? Also, what interfaces are seen on cluster nodes?

Best regards,
Victor

это встроенний код, не скрипт. выглядит он так:


      case DCM_AVERAGE_PER_MINUTE:
         nElapsedTime /= 60;  // Convert to minutes
      case DCM_AVERAGE_PER_SECOND:
         // Check elapsed time to prevent divide-by-zero exception
         if (nElapsedTime == 0)
            nElapsedTime++;

         switch(m_dataType)
         {
            case DCI_DT_INT:
               value = ((LONG)value - (LONG)m_prevRawValue) / (LONG)nElapsedTime;
               break;
            case DCI_DT_UINT:
               value = ((DWORD)value - (DWORD)m_prevRawValue) / (DWORD)nElapsedTime;
               break;
            case DCI_DT_INT64:
               value = ((INT64)value - (INT64)m_prevRawValue) / (INT64)nElapsedTime;
               break;
            case DCI_DT_UINT64:
               value = ((QWORD)value - (QWORD)m_prevRawValue) / (QWORD)nElapsedTime;
               break;
            case DCI_DT_FLOAT:
               value = ((double)value - (double)m_prevRawValue) / (double)nElapsedTime;
               break;
            case DCI_DT_STRING:
               // I don't see any meaning in "average delta per second (minute)" for string
               // values, so result will be 0 if there are no difference between
               // current and previous values, and 1 otherwise
               value = (LONG)((_tcscmp((const TCHAR *)value, (const TCHAR *)m_prevRawValue) == 0) ? 0 : 1);
               break;
            default:
               // Delta calculation is not supported for other types
               break;
         }


Quote from: Akira on March 27, 2012, 08:29:36 AM
28-Dec-2011 11:59:01   503850560
28-Dec-2011 10:59:01   795522378
28-Dec-2011 09:59:00   598589222
28-Dec-2011 08:59:00   9223372036854775807
28-Dec-2011 07:59:00   273392862
28-Dec-2011 06:59:00   163655688
28-Dec-2011 05:59:01   43122668
28-Dec-2011 04:59:01   86841056

Я так понимаю, происходит это когда предыдущее значение было больше, чем текущее.

Как можно сделать, чтобы при такой ситуации, просто считалось, что предыдущее значение = "0"?

Само по себе новое значение меньше предыдущего проблем вызывать не должно. Еcли параметр определен как unsigned и размер правильный, то все будет в порядке. Проблема может быть в несовпадении размера данных в DCI и на ноде - если реально данные 32 бита, а DCI определен как 64 бита, то при проходе счетчика через ноль как раз такой эффект и будет.

Rech' idet o management konsoli? Togda da, prosto sverhu raspakovat'. Pervij zapusk posle raspakovki poverh luchshe delat' komandoj

nxmc -clean

Voobsche nikakih otlichij ot predyduschih upgradeov bit' ne dolzno vrode.

That's very interesting, because at least on my system iostat's result are consistent with value given by NetXMS agent. Can you point me to exact place in iostat source code?

Best regards,
Victor

Hi!

/proc/diskstats has the following fields (numbering started after device name):

Field 1 — # of reads issued
Field 2 — # of reads merged
Field 3 — # of sectors read
Field 4 — # of milliseconds spent reading
Field 5 — # of writes completed
Field 6 — # of writes merged
Field 7 — # of sectors written
Field 8 — # of milliseconds spent writing
Field 9 — # of I/Os currently in progress
Field 10 — # of milliseconds spent doing I/Os
Field 11 — weighted # of milliseconds spent doing I/Os

NetXMS agent gets field #9 (# of I/Os currently in progress) to calculate average disk queue size. And "disk queue" means "number of disk I/O requests that are either in service or waiting for service". In iostat, it's a parameter called avgqu-sz (shown if running with -x command line option). On my NetXMS server it looks like this:


root@netxms:~# iostat -x 1
Linux 2.6.32-5-686 (netxms)     03/24/2012      _i686_  (2 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           8.26    0.00    2.39    3.24    0.00   86.11

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
cciss/c0d0        0.02    39.01    3.07   26.43   265.29   523.52    26.74     0.17    5.64   3.27   9.66

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           0.50    0.00    1.50    2.00    0.00   96.00

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
cciss/c0d0        0.00    13.00    0.00   13.00     0.00   208.00    16.00     0.05    4.00   4.00   5.20

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           3.45    0.00    1.48    0.49    0.00   94.58

Device:         rrqm/s   wrqm/s     r/s     w/s   rsec/s   wsec/s avgrq-sz avgqu-sz   await  svctm  %util
cciss/c0d0        0.00     8.00    0.00    3.00     0.00    88.00    29.33     0.02    6.67   4.00   1.20

^C
root@netxms:~# nxget 127.0.0.1 "System.IO.DiskQueue(cciss/c0d0)"
0.033333
root@netxms:~#


Best regards,
Victor

No, it's not possible, because each counter requires background processing, so agent have to know instance from the beginning, not only at DCI value request time. What I could think of simplifying counter configuration is to add option to WinPerf to collect all instances of a given counter. I'll add this as feature request.

Best regards,
Victor

Hi!

I hope that it will be before end of March, but I have planned quite a lot for this release, so maybe it will be delayed till first half of April, depending on how fast I'll be able to do development.

Best regards,
Victor

I would create a script which will get the file, parse it, and push values to NetXMS server using nxpush command. Then you can work with the values as usual - set thresholds, show history, etc.

Best regards,
Victor

You don't need two events, just two different rules for same event.

Also, if you want to put this logic into your script, it is also possible. You can just pass additional parameter to your script, giving current status of internet connection. In action definition, you can use macro %[script_name], and in the script return different values depending on internet connection state.

Best regards,
Victor

No, for your configuration you just have to add threshold for last value = 10000. ICMP.PacketLoss will work only for preconfigured targets (added by Target = ip_addr parameters in nxagentd.conf).

Best regards,
Victor

Hi!

I have some ideas why this can happen. I do some fixes already, next release will contain them. Hopefully it will help.

Best regards,
Victor

Hi!

I doubt that there are any possibility to access UPS from NetXMS agent in parallel with other software. The only good solution I could think of is to add additional functionality to UPS subagent, so it can shutdown server if UPS battery is running out. If this could be interesting, I will add it as feature request.

Best regards,
Victor