NetXMS Forum

image: grafana/grafana:5.2.1 works!

Thanks for everyone's help!
I guess we can close this.

I did attempt manually via:
grafana-cli plugins install radensolutions-netxms-datasource
and that did not help.

My normal install is automated using Docker Compose and bind mounting:

# Create the bind mount for Grafana
mkdir -p /opt/grafana
cp ldap.toml /opt/grafana/
chown -R 472:472 /opt/grafana
chmod a+rw -R /opt/grafana

# docker-compose.yml
version: '3.4'

services:

  # Grafana: https://hub.docker.com/r/grafana/grafana/
  grafana:
    image: grafana/grafana:5.2.0
    hostname: grafana
    environment:
      - GF_SERVER_PROTOCOL=http
      - GF_AUTH_LDAP_ENABLED=true
      - GF_AUTH_LDAP_CONFIG_FILE=/var/lib/grafana/ldap.toml
      - 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
    volumes:
      - type: bind
        source: /opt/grafana
        target: /var/lib/grafana
    networks:
      - logging-net1
    ports:
      - mode: host
        target: 3000
        published: 3000
    deploy:
      labels:
        local.description: "Grafana"

networks:
  logging-net1:

# Deploy to Docker
############
# Run Graylog on the Swarm
docker stack deploy -c docker-compose.yml grafana
# Verify
docker service ls | grep grafana

Then login to Grafana and try to add a new NetXMS data source and boom (see attached screen capture).
Note: The same docker-compose.yml above works fine with older versions of the Grafana Docker image, only changing one line:
    image: grafana/grafana:5.1.2  <--works
    image: grafana/grafana:5.1.3  <--works
    image: grafana/grafana:5.2.0  <--fails as described

---

I tried on new and old and reinstalled the plugin, no joy on adding a new NetXMS data source on 5.2.0 - see attached screen capture

---

The NetXMS Grafana data source plugin does not work (it gives an error and won't load the data source plugin page correctly).

I run Grafana in a container and deploy via Docker Compose, so my environment is controlled carefully.

History:
Grafana 5.1.2 = works ok with NetXMS data source plugin
Grafana 5.1.3 = works ok with NetXMS data source plugin
Grafana 5.1.4 = Grafana folks broke LDAP, could not use this version
Grafana 5.2.0 = LATEST (adds fixes needed for other stuff I use) <-- NetXMS data source plugin fails to load

Error:

Plugin Error
Failed to fetch Instantiating https://newen008-grafana.pims.presidio.com/public/vendor/plugin-css/css.js Loading https://newen008-grafana.pims.presidio.com/public/vendor/plugin-css/css.js Instantiating https://newen008-grafana.pims.presidio.com/public/plugins/radensolutions-netxms-datasource/css/query-editor.css!https://newen008-grafana.pims.presidio.com/public/vendor/plugin-css/css.js Loading https://newen008-grafana.pims.presidio.com/public/plugins/radensolutions-netxms-datasource/query_ctrl.js Loading plugins/radensolutions-netxms-datasource/module

This leaves us in a bad position.
I need Grafana 5.2.0 for the latest fixes for my other stuff (Elastic)
but
Only Grafana 5.1.3 (and older) works with the NetXMS data source plugin.

Can anyone please take a look and update the NetXMS data source plugin to work with Grafana 5.2.0 (and higher)?

---

Thank you for responding. I will definitely take a look at the example, but sadly I do not normally program in that language. I am wondering if having an MQTT integration that is bi-directional could help in this case? I do a lot of work in node js and I am okay in Python, so it would be nice when version 3.0 is available.

I have not had very much success with MQTT. It is very likely my fault, I am sure I'm doing things wrong. I have been following the guide documentation, but nothing is really working and I don't even see a connection happening. Does anyone have a step-by-step guide and or additional information about MQTT?

What options do we have available for integrating with external ticket systems?
For example, can we send outbound webhooks from netxms? Can we send out bound mqtt messages?
I am interested in the hearing about any external integration including and especially anything that is bi-directional. It would be nice to Open tickets in an external system and it would be even nicer if when those tickets got updated, the alarm got acknowledged and a ticket number was placed with the alarm. Does anyone have any guidance or thoughts on this topic?

Victor,

Thank you for the reply and for making and releasing awesome software!

SOLVED:
The problem was a spelling error!

NOT with an "e":
seperator

Correct spelling:
separator

Ughh facepalm!
Sorry for the false alarm.

Thank you,
Ernest
https://www.linkedin.com/in/ernestgwilsonii/

How do you specify a tab delimiter when using external table?
separator=\t
or
separator=\\t
or
separator=\\\t
or
other?
Nothing is working for me.

We are not using Jira and we want to integrate with various ticket systems.
Currently we have alerts calling a shell script that calls curl via the command line to make API calls.
Today these calls post messages into our chat channel.
We would like to start opening, updating and closing tickets instead of just spamming our chat channel.
Before we just update our shell script (that uses curl) to make API calls into our ticket system (which we can do), we want to get some feedback please:

1. Is there a preferred method for integrating external systems? (We could have a ton of shell execs kicking off curl API calls under heavy ticket volume, that seems not optimal)
   Is there any specific hooks or methods or pub/sub inside or bolted on to NetXMS we should use?

2. What about inbound (and/or two-way) integration to NetXMS from ticket systems?
   If a person acknowledges a ticket in a ticket system for example, is there a way to add fields mapped back to alerts in NetXMS and indicate things like ticket #1234 is open and owned by John Doe?

What options currently exist?
What is considered to be the "NetXMS" way?
What are most folks doing in this area (we are not looking to reinvent the wheel if tooling already exists)?

Thank you,
Ernest