Process Dispatcher down when BDD is no longer available about horus HOT 2 CLOSED

Hi,

It was done "on purpose" at the time as the db connection is essential for the dispatcher to work. The idea was to let it crash and let systemd (or any other supervisor) restart it in a clean state when db is available again.

It looks like you are using Horus in a very interesting way, I would love to hear more about it :) Feel free to contact me by PM (my email is in my profile.)

from horus.

Hi,

I handled this feature with "systemd" and it works fine.

We also use the "tags" field of the "devices" table which allows you to add labels. This feature works well but does not expose the labels in the "pingmetrics" metrics. It exposes tags only in the results of the "snmpmetrics" metric.

Examples:

champs "tags": {Communaute="TEST", location="TEST"} for devices "xxxxxxxxxxxxxx"

snmpmetrics:

ifMetrics_ifMtu{Communaute="TEST",category="Network Terminaison Equipment",host="xxxxxxxxxxxxxx",id="1",ifDescr="ETHERNET NETWORK PORT",ifName="NETWORK PORT-1-1-1-2",index="2",location="TEST",model="NTE",oid=".1.3.6.1.2.1.2.2.1.4",vendor="GENERIC"} 9612 1638376611615

pingmetrics: We don't see the tags label "Communaute" and "location".

ping_min_duration_seconds{category="Network Terminaison Equipment",host="xxxxxxxxxxxxxx",id="1",ip_address="yyyyyyyyy",model="NTE",vendor="GENERIC"} 0.01567 1638518891194

Our next challenge will be to create a Horus "docker".

Br,

Chris.

from horus.