Maxime Wojtczak
Maxime Wojtczak
We need this, even a more up-to-date version!
Hello, This is currently not supported: the same trap OID is sent, with a status field. This may be an interesting feature though.
Hello, These is no way right now to update configuration during runtime. Given the image relies on environment variables & command-line, your deployment/pods should be updated as soon as there...
Thanks for your detailed message. If after your modification of the parser, it worked as you expected, I propose you to use the `.DeclaredAlerts` variable in your template, which includes...
I'm gonna do some checks, as the default template seems to work well: ``` {{ len .Alerts }}/{{ len .DeclaredAlerts }} alerts are firing: ``` And it always display the...
@fabienmagagnosc I just merged some new options, including optional a resolution trap OID. Please, check the README: https://github.com/maxwo/snmp_notifier?tab=readme-ov-file#snmp-notifier-configuration It is not yet released. I need to do some extra checks,...
Closing due to inactivity
> it seems that the addition of the fields inside the traps is not "order incrementally" > > **for subOid, template := range trapSender.configuration.ExtraFieldTemplates {** True. I will ensure it...
Issue is solved: it was due to the use of an hash-map for reading command line arguments, which does not guarantee the order of elements. I will release after another...
@fabienmagagnosc FYI, fix has been released in 1.6.2