Comments
-
Is there anyway to use the API to update a custom SWQL table though? Seems like I have to either edit it manually or try to connect directly to the DB with python (which is a bit of a hassle in our environment with Windows authentication from Linux)
-
Thanks, so its not used and not able to be used. Are there any ways you can think of to be able to write descriptions per routing neighbor that can be used in alert emails? Currently the only way I've thought to do that is with create a separate SQL table, but then that must be updated through SQL and not the API. If there…
-
Not seeing where that post relates to the Description field that can be found in the API, am I missing something?
-
Bump, anyone have ideas? How can this field be used? Would be nice to be able to write to it via API instead of having a blank description field for every neighbor.
-
There are MANY possible IPs :) Just looking at the syslog: May 14 18:35:32: %BGP-5-ADJCHANGE: neighbor x.x.x.x Down User reset There is a default log for this, but I am using the routing neighbor alert for that use case. The only issue with that is you can only poll the routing neighbors once per minute, and I have it set…
-
How would you pick specific pieces from that log message though? IE regex for the IP address. Right now I was trying to have an alert created after a log was seen 3 times in 15 minutes, but I would want it created only if the log related to the same IP (like a BGP neighbor flapping) is involved. Currently if 3 different…
-
Is there a definition anywhere of what information should be populated in this description? Where would you find this in the GUI? I've only seen this referenced in the API. Under Network I see this, but there is no description field.
-
Yep, all of the other information is populated, but none of the 200+ routing neighbors have any information in Description. When I try to run an update against it to add my own info, it is not allowed.