NetXMS Forum

Unfortunately I have not managed to recreate this issue, could you prepare a curl request and post the results?

Hi!

Yes, it is possible, for the available requests have a look at this documentation page: https://www.netxms.org/documentation/adminguide/advanced.html#web-api-rest-api. The WebApi is currently in early development but it will soon be updated with many more features!

Regards,
Eriks

Hi!

I just deployed Grafana on Docker and everything seems to be working, I installed the same plugins on the same version of Grafana you are using (5.2.0). Could you try deploying the container without swarm? If it works, then the problem could be somewhere in your configuration, this is the command I used docker run -e "GF_SERVER_PROTOCOL=http" -e "GF_INSTALL_PLUGINS=grafana-clock-panel,grafana-simple-json-datasource,grafana-piechart-panel,percona-percona-app,raintank-kubernetes-app,ntop-ntopng-datasource,natel-plotly-panel,camptocamp-prometheus-alertmanager-datasource,vonage-status-panel,fetzerch-sunandmoon-datasource,radensolutions-netxms-datasource" -d --name=grafana -p 3000:3000 grafana/grafana:5.2.0
Also I noticed that Grafana version 5.2.1 is available, maybe that will solve the issue.

Regards,
Eriks

Hi!

Could you specify how you installed the plugin? Was it via the Grafana client using the command grafana-cli plugins install radensolutions-netxms-datasource or did you clone the GitHub repository of the plugin?

Hi!

I've just tested the plugin with the latest version of Grafana (5.2.0) and all seems to be working for me. Could you please reinstall the NetXMS plugin and see if it changes anything?

Regards,
Eriks

Hi!

Are you sure that the DCI has collected enough data to be plotted? I can only achieve your described behaviour when I've just started the server, agent and grafana.

Regards,
Eriks

Hi!

If grafana is running in https mode, it will not accept datasources which are not from https url's.
The guide is a bit of a hack to get the API working with the same built in web server that comes with the windows WebUI installation. What I can suggest is to deploy a dedicated web server like Apache Tomcat and following this guide, configure it for SSL usage https://www.mulesoft.com/tcat/tomcat-ssl

Regards,
Eriks

Hi! There is currently no way around it. I have created an Issue on our tracker who`s progress you can follow on this link https://track.radensolutions.com/issue/NX-1400

Regards,
Eriks

Hi!

Could you check if the DCI has collected any data? Also, could you please post screenshots of the DCI configuration?

Regards,
Eriks

Hi!

You can find documentation on how to use the MQTT subagent in our admin guide: https://www.netxms.org/documentation/adminguide/hardware-monitoring.html#mqtt

Regards,
Eriks

Hi!

Yes, there is! You can find it in the management console under View --> Alarm log, there you can set custom filters to show the alarm history of specific devices. The size of the alarm history can by configured using this server configuration parameter "AlarmHistoryRetentionTime" which will set the number of days to keep the alarm history.

Regards,
Eriks

We are starting to implement tags for debug messages so that particular debug messages could be filtered, but unfortunately this has not been done yet for the messages in question.

Hi,

If you have debug level 5 enabled, please check your server logs for a message that is similar to this: "DataCollectionTarget::updateInstances(%s [%u], %s [%u]): instance \"%s\" not found, grace period started" without the "%s and %u symbols. This should indicate that the grace period was actually started as it is what triggers the re-enabling of the instance. It could be an issue that the instance went into an unsupported state for a different reason and was not re-enabled by instance discovery.

Hi!

Could you run instance discovery on the node manually and post a screenshot of the output?

Hi! We have moved our netXMS repository to github, you can find it at https://github.com/netxms/netxms.

Regards,
Eriks

It shouldn`t change anything, it was just a guess :).
Could you let me know which Linux distribution you are using, what kernel etc... Also, which version of Windows?

Could you try changing the PING subagent section in config to uppercase? As in:

*PING
DefaultPacketSize = 46
...

Could you, please, provide the output of "nxagentd -C"? Don`t forget to edit out any sensitive data, I am interested specifically in the PING subtree.

Ok and is there anything in the log similar to this line: "Unable to add ICMP ping target from configuration file."?

Could you please verify that the PING subagent is in the list opened by Right click on pinging node -> Tools -> Info -> Agent -> Subagent list. And that you get this entry in your agent log once it is started:

*I* Subagent "PING" (ping.nsm) loaded successfully (version 2.2.1-14-g375721606)