Hi! We’re trying to integrate one server that has all the visualization capabiltiies, with our Chirpstack server in order to visualize telemrtry
This is PRTG which seems to have little native compatibilty with CS…
Se having a MQTT server up on CS server, and having the ability to connect thru MQTT from out PRTG server, can we use the builtin MQTT server in CS to interchange telemetry between these two servers?
Any risk in it?
Any specific setup to keep in mind?
Thanks
What do you mean by “builtin MQTT”? Do you mean the Mosquitto MQTT broker that the reference docker-compose file brings up, which isn’t developed by Brocaar? I don’t see why you cannot use it for other purposes. As with everything, please do configure it to fit your requirements. If it’s for production use, it should be configured to be production-grade.
No risk to it, the only topics Chirpstack actually uses itself are the ones starting with <region-prefix.>/gateway/…, those are the messages directly to/from the gateways and are still encrypted, you should not touch these as they are what Chirpstack actually runs off. The messages starting with “application/” are the “integration events” and are decrypted versions of the <region-prefix.> events, only displayed for debugging or integration purposes such as what you are describing. You should be able to get all the information you need to display telemetry in PRTG using those application/ topics.
Ok so I don’t even have to do anything on it so it would, by default, post all telemetry on MQTT?
Sounds easy then!
Thanks
Yup! Anything you see in the device events in the UI is just a reformatting of the application/ MQTT messages. And if for whatever reason you want to send those “integration events” to a seperate MQTT broker you can configure that in the [integration.mqtt] section of your chirpstack.toml.
I’m not familiar with prtg, but you will likely have to do some reformatting of the MQTT messages in order for the platform to use them effectively.