Monitoring the health of the network


#1

Hey folks,

At present I’m monitoring Nginx/RabbitMQ/PostgreSQL/etc. but I’m wondering how I get the number of gateways, gateway health, and other LoRaServer-specific metrics out of the platform.

I’ve looked at https://www.loraserver.io/lora-gateway-bridge/use/data/ however that involves being subscribed to a particular MQTT channel. I’ll go down this route if I have to, but I was hoping that there was an HTTP endpoint which would expose these metrics so I can simply CURL them.

Thanks in advance,

Matt


#2

I should probably point out that I don’t actually use the Lora Gateway Bridge - all my gateways are Laird RG1xx and connect via MQTT, so I can’t use the Prometheus collector either.


#3

The plan is to also provide Prometheus metrics in LoRa (App) Server in the future :slight_smile:


#4

Awesome, that’s good news, especially as our monitoring solution of choice (DataDog) can ingest prometheus stats by default! :slight_smile:


#5

Hey Brocaar - Is Prometheus something that’s a work in progress? We would love that to be present in loraserver and app server components as well and that’s something we would be happy to contribute too.


#6

@brocaar Not sure if you had a chance to see my message above.


#7

Are you aware about this link available here ==> https://www.loraserver.io/community/links/

http://lorhammer.itk.fr/ maybe this is not the same purpose?


#8

Lorhammer is for load-testing as opposed to systems monitoring.

At the moment, I’m monitoring RabbitMQ, Nginx, checking that the various LoRaServer processes, and the PGSQL database, but what I’d love to be able to get the metrics on is number of gateways attached, time taken to process messages within LoRaServer.io etc, all the things that let me know that the various parts of LoRaServer are working as expected and that allow me to spot when things are starting to go wrong.

Lorhammer is awesome, but as you can see from the bug I logged at https://gitlab.com/itk.fr/lorhammer/issues/92, there are some issues with the way it works because of changes in the LoRaServer API.