Now Signalilo creates unique services with IDs based on: ${alertname}_${fingerprint} and give them names as: ${alertname} to have more nice output in Web UI, but when Icinga used as server in Nagstamon this results in the fact that Nagstamon will display only 1 alert from a bunch of alerts with same servicename.
It would be cool if Signalilo could support an optional workaround for it:
set display service name as ${alertname}_${fingerprint}
set servicename as-is
This logic could be controlled by a command flag or environment variable, while by default it will work as-is.
Additionally, support nice servicename as ${alertname}_${id}, where ${id} is an incremental integer? Would be cool, but not sure it's possible or worth the effort. As it means that we need to check for any existing ${alertname}_${id} before creating alert, not think Icinga could return service not by its IDs, but by display servicename. Maybe a sort of search request with filter by ${alertname}_ is possible?
Now Signalilo creates unique services with IDs based on:
${alertname}_${fingerprint}and give them names as:${alertname}to have more nice output in Web UI, but when Icinga used as server in Nagstamon this results in the fact that Nagstamon will display only 1 alert from a bunch of alerts with same servicename.It would be cool if Signalilo could support an optional workaround for it:
${alertname}_${fingerprint}This logic could be controlled by a command flag or environment variable, while by default it will work as-is.
Additionally, support nice servicename as
${alertname}_${id}, where${id}is an incremental integer? Would be cool, but not sure it's possible or worth the effort. As it means that we need to check for any existing${alertname}_${id}before creating alert, not think Icinga could return service not by its IDs, but by display servicename. Maybe a sort of search request with filter by${alertname}_is possible?Thank you in advance!