You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a prefix is configured with ignore: true and an ASN covered by monitorASns announces the prefix a misconfiguration is emitted.
Per the documentation ignore should Exclude the current prefix from monitoring. Useful when you are monitoring a prefix and you want to exclude a particular sub-prefix, which I interpret to mean we shouldn't alert for things related to this prefix.
Currently this appears to work for prefix monitoring (monitorHijack, monitorNewPrefix, monitorPath, monitorVisibility), but not for AS monitoring.
When AS65001 announces 172.111.69.96/27 no message is emitted from BGPalerter.
When AS65001 withdraws 172.111.69.96/27 no message is emitted from BGPalerter.
Currently 2 is happening, however for the AS path monitor it is being logged/notified;
$ cat reports-2019-12-15.log
[production] verbose: AS65001 is announcing 172.111.69.96/27 but this prefix is not in the configured list of announced prefixes
Thanks for reporting. I think your pull request is also perfect.
I'm going to merge this in dev (the next release is close) and upload a new pre-release binary for you to use in the meanwhile.
Describe the bug
When a prefix is configured with
ignore: true
and an ASN covered by monitorASns announces the prefix a misconfiguration is emitted.Per the documentation
ignore
shouldExclude the current prefix from monitoring. Useful when you are monitoring a prefix and you want to exclude a particular sub-prefix
, which I interpret to mean we shouldn't alert for things related to this prefix.Currently this appears to work for prefix monitoring (monitorHijack, monitorNewPrefix, monitorPath, monitorVisibility), but not for AS monitoring.
Provide an example
config.yml
prefixes.yml
Expected behavior
Currently 2 is happening, however for the AS path monitor it is being logged/notified;
Are you using the binary or the source code?
Binary;
The text was updated successfully, but these errors were encountered: