Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

E

Egert143

@Egert143
Unfollow Follow
About
Posts
265
Topics
106
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Possilbe bug: Float DCI values below 1 display unnecessary trailing zeroes with
    E Egert143
    Support

    Float DCI values between approximately 0.01 and 1 are displayed with unnecessary trailing zeroes when using a measurement unit with default multipliers.

    For example, I am monitoring current from a PDU over SNMP.

    The SNMP device returns integer values that are divided by 100 using a transformation script:

    return $1 / 100;

    For a phase current:

    Raw value: 303
    Transformed value: 3.03
    Displayed value: 3.03 A

    This is displayed correctly.

    However, for the neutral current:

    Raw value: 68
    Transformed value: 0.68
    Displayed value: 0.680000 A

    The expected display value would be:

    0.68 A
    Configuration
    NetXMS server/client version: 6.1.1
    DCI type: SNMP
    Data type: Float
    Unit: A
    Multipliers: Default
    Transformation:
    return $1 / 100;
    Steps to reproduce
    Create an SNMP DCI returning an integer value such as 68.
    Set the DCI data type to Float.
    Set the measurement unit to A.
    Leave multipliers at the default setting.
    Add the transformation:
    return $1 / 100;
    The transformation test correctly shows 0.68.
    After normal data collection, Last Values displays:
    0.680000 A

    Using the same configuration with a raw value such as 303 produces:

    3.03 A

    as expected.

    I also duplicated a working DCI that displayed 3.03 A correctly and changed only the SNMP OID so that the returned/transformed value was below 1. The duplicated DCI immediately showed the same 0.680000 A behavior, so the issue does not appear to be caused by a DCI configuration difference.

    Expected behavior

    Float values should use consistent formatting regardless of whether the value is above or below 1.

    For example:

    3.030000 -> 3.03 A
    0.680000 -> 0.68 A
    Actual behavior

    Values greater than or equal to 1 are formatted without unnecessary trailing zeroes:

    3.030000 -> 3.03 A

    while values below 1 may retain the complete float string:

    0.680000 -> 0.680000 A
    Additional information

    The behavior appears to still be present in the DataFormatter implementation in NetXMS 6.2.3 and current master.

    It appears that when the default multiplier logic cannot select a multiplier for a value below 1, the original value string is retained instead of being converted to a Double. The %s formatting path then only applies the normal decimal formatting when the value is a Double, causing the original 0.680000 string to be displayed unchanged.

    The underlying numeric DCI value appears to be correct; this seems to be a display/formatting issue.


  • Monitoring ubuntu service status
    E Egert143
    Support

    Hello

    What are the steps to monitor ubuntu service status?

    Egert


  • Slow GUI
    E Egert143
    Support

    Yes, that's correct.


  • Slow GUI
    E Egert143
    Support

    PC usage is relatively low. The i7-10875H CPU is utilized at about 20%, and out of 32GB of RAM, 40% is in use. This is the total PC usage.
    In the debug log, I see a large amount of traffic, for example:

    2024.11.06 09:55:42.798 *D* [client.session.7   ] Sending message CMD_NODE_DCI (16 bytes)
    2024.11.06 09:55:42.809 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
    2024.11.06 09:55:42.809 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
    2024.11.06 09:55:42.826 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
    2024.11.06 09:55:42.826 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
    2024.11.06 09:55:42.864 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (1256 bytes)
    2024.11.06 09:55:42.867 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (912 bytes)
    2024.11.06 09:55:42.870 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (912 bytes)
    2024.11.06 09:55:42.873 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (888 bytes)
    2024.11.06 09:55:42.875 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (928 bytes)
    2024.11.06 09:55:43.179 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:43.179 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.181 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:43.181 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:43.181 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.181 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.182 *D* [client.session.7   ] Received message CMD_GET_NODE_DCI_LIST
    2024.11.06 09:55:43.183 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.183 *D* [client.session.7   ] Sending message CMD_NODE_DCI (16 bytes)
    2024.11.06 09:55:43.194 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
    2024.11.06 09:55:43.194 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
    2024.11.06 09:55:43.204 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
    2024.11.06 09:55:43.204 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
    2024.11.06 09:55:43.517 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:43.517 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.519 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:43.519 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:43.519 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.519 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.520 *D* [client.session.7   ] Received message CMD_GET_NODE_DCI_LIST
    2024.11.06 09:55:43.520 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:43.521 *D* [client.session.7   ] Sending message CMD_NODE_DCI (16 bytes)
    2024.11.06 09:55:43.536 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
    2024.11.06 09:55:43.536 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
    2024.11.06 09:55:43.557 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
    2024.11.06 09:55:43.557 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
    2024.11.06 09:55:43.657 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (1328 bytes)
    2024.11.06 09:55:44.061 *D* [client.session.7   ] Sending compressed message CMD_EVENTLOG_RECORDS (192 bytes)
    2024.11.06 09:55:44.223 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:44.223 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:44.224 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:44.224 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
    2024.11.06 09:55:44.225 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:44.225 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:44.226 *D* [client.session.7   ] Received message CMD_GET_NODE_DCI_LIST
    2024.11.06 09:55:44.226 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
    2024.11.06 09:55:44.227 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (728 bytes)
    2024.11.06 09:55:44.228 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (600 bytes)
    2024.11.06 09:55:44.229 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (600 bytes)
    2024.11.06 09:55:44.231 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (896 bytes)
    2024.11.06 09:55:44.232 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (776 bytes)
    2024.11.06 09:55:44.234 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (752 bytes)
    2024.11.06 09:55:44.235 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (1040 bytes)
    2024.11.06 09:55:44.236 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (760 bytes)
    2024.11.06 09:55:44.237 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (792 bytes)
    2024.11.06 09:55:44.238 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (568 bytes)
    2024.11.06 09:55:44.239 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (568 bytes)
    2024.11.06 09:55:44.240 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (576 bytes)
    2024.11.06 09:55:44.240 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
    2024.11.06 09:55:44.242 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (776 bytes)
    2024.11.06 09:55:44.242 *D* [client.session.7   ] Sending compressed message CMD_REQUEST_COMPLETED (1776 bytes)
    2024.11.06 09:55:44.243 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (776 bytes)
    2024.11.06 09:55:44.245 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (792 bytes)
    2024.11.06 09:55:44.246 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (792 bytes)
    2024.11.06 09:55:44.247 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (656 bytes)
    

    Not sure if it was a coincidence, but as soon as I started debugging, the GUI felt a lot more responsive, with objects loading almost instantly. However, after restarting the client, the GUI returned to being slow, and re-enabling debug mode did not improve speed this time, so it was likely random.

    In the NetXMS server log, I see endless entries like this:

    2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
    2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
    2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
    2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
    2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
    2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
    2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
    

    This appears to be what's causing the failed SQL queries.
    I also asked other NetXMS client users, and they reported a slow GUI as well, which they noted likely started with version 5.


  • Slow GUI
    E Egert143
    Support
    show threads:
    
    
    MAIN
       Threads.............. 64 (64/512)
       Load average......... 0.00 0.00 0.00
       Current load......... 0%
       Usage................ 12%
       Active requests...... 0
       Scheduled requests... 1
       Total requests....... 4667321
       Thread starts........ 0
       Thread stops......... 0
       Wait time EMA........ 1 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    AGENT
       Threads.............. 4 (4/256)
       Load average......... 0.00 0.00 0.00
       Current load......... 0%
       Usage................ 1%
       Active requests...... 0
       Scheduled requests... 0
       Total requests....... 40449212
       Thread starts........ 1
       Thread stops......... 1
       Wait time EMA........ 0 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    POLLERS
       Threads.............. 762 (600/1200)
       Load average......... 581.33 450.22 410.93
       Current load......... 51%
       Usage................ 63%
       Active requests...... 392
       Scheduled requests... 0
       Total requests....... 3069782028
       Thread starts........ 31888
       Thread stops......... 31726
       Wait time EMA........ 8 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 7
       Queue size SMA....... 0
       Queue size SD........ 0
    
    FILE-TRANSFER
       Threads.............. 2 (2/16)
       Load average......... 0.00 0.00 0.00
       Current load......... 0%
       Usage................ 12%
       Active requests...... 0
       Scheduled requests... 0
       Total requests....... 0
       Thread starts........ 0
       Thread stops......... 0
       Wait time EMA........ 0 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    NPE
       Threads.............. 1 (1/1024)
       Load average......... 0.00 0.00 0.00
       Current load......... 0%
       Usage................ 0%
       Active requests...... 0
       Scheduled requests... 0
       Total requests....... 0
       Thread starts........ 0
       Thread stops......... 0
       Wait time EMA........ 0 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    DATACOLL
       Threads.............. 600 (600/1200)
       Load average......... 7.95 11.07 11.24
       Current load......... 0%
       Usage................ 50%
       Active requests...... 3
       Scheduled requests... 0
       Total requests....... 2207466859
       Thread starts........ 6
       Thread stops......... 6
       Wait time EMA........ 0 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    CLIENT
       Threads.............. 16 (16/2048)
       Load average......... 2.61 1.36 1.19
       Current load......... 56%
       Usage................ 0%
       Active requests...... 9
       Scheduled requests... 0
       Total requests....... 163569444
       Thread starts........ 21
       Thread stops......... 21
       Wait time EMA........ 0 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    SYNCER
       Threads.............. 4 (4/4)
       Load average......... 0.00 0.00 0.43
       Current load......... 0%
       Usage................ 100%
       Active requests...... 0
       Scheduled requests... 0
       Total requests....... 228080205
       Thread starts........ 0
       Thread stops......... 0
       Wait time EMA........ 193 ms
       Wait time SMA........ 137 ms
       Wait time SD......... 65 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    DISCOVERY
       Threads.............. 8 (8/16)
       Load average......... 0.00 0.00 0.00
       Current load......... 0%
       Usage................ 50%
       Active requests...... 0
       Scheduled requests... 0
       Total requests....... 3105
       Thread starts........ 0
       Thread stops......... 0
       Wait time EMA........ 2 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    SCHEDULER
       Threads.............. 1 (1/64)
       Load average......... 0.00 0.00 0.00
       Current load......... 0%
       Usage................ 1%
       Active requests...... 0
       Scheduled requests... 1
       Total requests....... 43036
       Thread starts........ 0
       Thread stops......... 0
       Wait time EMA........ 0 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    
    MOBILE
       Threads.............. 4 (4/256)
       Load average......... 0.00 0.00 0.00
       Current load......... 0%
       Usage................ 1%
       Active requests...... 0
       Scheduled requests... 0
       Total requests....... 0
       Thread starts........ 0
       Thread stops......... 0
       Wait time EMA........ 0 ms
       Wait time SMA........ 0 ms
       Wait time SD......... 0 ms
       Queue size EMA....... 0
       Queue size SMA....... 0
       Queue size SD........ 0
    

  • Slow GUI
    E Egert143
    Support

    Hello

    What could cause slow gui response, curent version 5.0.5?

    For example if i navigate the object tree, then sub folders opening speed is sometimes very slow. and clicking on random node, then information tabs load slow sometimes. Is it more sql problem ?

    show dbstats:
    
    SQL query counters:
       Total .......... 4922790645
       SELECT ......... 458044306
       Non-SELECT ..... 4464754025
       Long running ... 0
       Failed ......... 12131046
    Background writer requests:
       DCI data ....... 1779941668
       DCI raw data ... 1983730639
       Others ......... 10013301
    
    show stats:
    Objects............: 60590
       Nodes...........: 7909
       Interfaces......: 46960
       Access points...: 1492
       Sensors.........: 0
    Collectible DCIs...: 23509
    Active alarms......: 5610
    Uptime.............: 123 days,  6:38:56
    

    Egert


  • MQTT with json format
    E Egert143
    Support

    Seems like setting MQTT proxy solved the problem. Thanks!

    Egert


  • MQTT with json format
    E Egert143
    Support

    Can it be version problem, i currently run V5.0.5?

    In agent logs i get following:

    config

    2024.11.04 12:23:22.778 *I* [config            ]  +- CORE
    2024.11.04 12:23:22.778 *I* [config            ]  |  +- DebugLevel
    2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: 6
    2024.11.04 12:23:22.778 *I* [config            ]  |  +- MasterServers
    2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: 192.168.3.73
    2024.11.04 12:23:22.778 *I* [config            ]  |  +- ConfigIncludeDir
    2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: C:\NetXMS\etc\nxagentd.conf.d
    2024.11.04 12:23:22.778 *I* [config            ]  |  +- LogFile
    2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: C:\NetXMS\log\log.txt
    2024.11.04 12:23:22.778 *I* [config            ]  |  +- FileStore
    2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: C:\NetXMS\var
    2024.11.04 12:23:22.778 *I* [config            ]  |  +- SubAgent
    2024.11.04 12:23:22.778 *I* [config            ]  |        value: winperf
    2024.11.04 12:23:22.778 *I* [config            ]  |        value: mqtt
    2024.11.04 12:23:22.778 *I* [config            ]  +- MQTT
    2024.11.04 12:23:22.778 *I* [config            ]      +- Brokers
    2024.11.04 12:23:22.778 *I* [config            ]          +- Local
    2024.11.04 12:23:22.778 *I* [config            ]              +- Hostname
    2024.11.04 12:23:22.778 *I* [config            ]                  value: 127.0.0.1
    ...
    2024.11.04 12:23:23.214 *D* [mqtt               ] 0 MQTT parameters added from configuration
    2024.11.04 12:23:23.214 *D* [mqtt               ] Using libmosquitto 2.0.15
    2024.11.04 12:23:23.214 *D* [mqtt               ] Automatic registration of MQTT topics is enabled
    2024.11.04 12:23:23.214 *I* [subagents          ] Subagent "MQTT" (mqtt.nsm) loaded successfully (version 5.0.1)
    2024.11.04 12:23:23.214 *D* [mqtt               ] Connected to MQTT broker 127.0.0.1:1883 as anonymous
    

  • MQTT with json format
    E Egert143
    Support

    So i need only following in agent config ?

    [MQTT/Brokers/Test]
    Hostname = y.y.y.y
    Port = 1883
    

    I made new DCI:
    Origin: mqtt
    Metric: Test:metrics/grid/voltage/L1
    Data type: Float

    Btw the Broker is in same server as agent itself, if it makes difference. With mqtt explorer i see that value changes every few seconds. Yet dci remains in not supported status.


  • MQTT with json format
    E Egert143
    Support

    Hello, i did agent config as following:

    MasterServers = x.x.x.x
    ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
    LogFile = {syslog}
    FileStore = C:\NetXMS\var
    SubAgent = mqtt
    SubAgent = winperf
    
    [MQTT/Brokers/Test]
    Hostname = y.y.y.y
    Port = 1883
    [MQTT/Brokers/Test/Metrics]
    Volt = "metrics/grid/voltage/L1"
    

    the output looks like this:

    {
      "timestamp": "2024-10-30T09:42:12.145495",
      "type": "float",
      "value": 236.21934509277344
    }
    

    how can i extract the value ?

    Currently in netxms i just get unsuported.


  • Monitoring log file, and alerting when no new logs in x time
    E Egert143
    Support

    Hello

    Is it possible to monitor windows log file for specific log, example "C:\ProgramData\Program1\Logs\log1.log", that contains 1 new entry every time that program succesfully runs. i would like to get notified when there has not been new log entry in X ammount of time. And to make matters more fun, there can be different log lines, but i am looking for specific content.

    Demo line: "2024-06-25 08:59:39.677+03:00 [    61] INFO      - RuleProcessor starting to execute rule action. Rule: 45df1829-4617-4a39-8933-36799aa6f466 (! TEST !); ActionName: VideoOS.Server.RuleActions.LogServerEntryRuleAction"


  • Management client slow after upgrade
    E Egert143
    Support

    New desktop client. Ping time is ~1ms.


  • Management client slow after upgrade
    E Egert143
    Support

    Hello

    After upgrading to version 5.0.1 users have noticed that Management client feels slower, what might cause this, and what to check for performance bottlenecks ?

    Egert


  • NetXMS 5.0 released
    E Egert143
    Announcements

    when i create new node with fresh dci-s then they appears normal again.


    dci_sample.png


  • Monitoring gpu on windows
    E Egert143
    Support

    Is it possible to detect gpu model on windows system and also monitor usage?


  • NetXMS 5.0 released
    E Egert143
    Announcements

    What do the yellow DCI mean? they collect data but are yellow.

    also script says function "CreateSNMPTransport" and "SNMPGetValue" are deprecated, what are replacements?


  • NetXMS 5.0 released
    E Egert143
    Announcements

    Why do most data collection entries appear as yellow after upgrade, but they are still collecting metrics?

    and i see error "Script(DCI::NODE-NAME::177748::InstanceFilter) execution error: Error in line 1: sytnax error, unexpected '?', expecting $end" Where can i find the script that is generating this error ?

    update was done directly to 5.0.1.


  • NetXMS 5.0 released
    E Egert143
    Announcements

    I was looking for the server installer for windows and saw that now support is needed for this. That is why i asked if it was no longer free.

    is building windows installer for server from source complex task ? 🙂


  • NetXMS 5.0 released
    E Egert143
    Announcements

    Hello

    Is NetXms no longer free starting with version 5?


  • NetXMS 4.5 patch release 6
    E Egert143
    Announcements

    After upgrade i noticed that infrastructer object browser doesent auto refresh anymore, for example container binding or renaming. user has to press manual refresh.

  • Login

  • Don't have an account? Register

  • Login or register to search.
Powered by NodeBB Contributors
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups