This can be interesting to perform some troubleshoot such as the issue that drops BGP sessions and keeps the dr-agent active on Neutron [1]. However, for observability purposes, I believe that the information in the logs can help in obtaining the status and triggering alarms.
neutron-bgp-dragent[907]: neutron_dynamic_routing.services.bgp.agent.driver.os_ken.driver [-] BGP Peer IPv6-Peer-Address for remote_as=XXX went DOWN.
neutron-bgp-dragent[907]: neutron_dynamic_routing.services.bgp.agent.driver.os_ken.driver [-] BGP Peer IPv6-Peer-Address for remote_as=XXX is UP.
Now, in case this "local" ssh session gets realtime session status, I'd like to see it exported to an integrated tool like Prometheus :)
Hello Yusuf,
This can be interesting to perform some troubleshoot such as the issue that drops BGP sessions and keeps the dr-agent active on Neutron [1]. However, for observability purposes, I believe that the information in the logs can help in obtaining the status and triggering alarms.
neutron- bgp-dragent[ 907]: neutron_ dynamic_ routing. services. bgp.agent. driver. os_ken. driver [-] BGP Peer IPv6-Peer-Address for remote_as=XXX went DOWN. bgp-dragent[ 907]: neutron_ dynamic_ routing. services. bgp.agent. driver. os_ken. driver [-] BGP Peer IPv6-Peer-Address for remote_as=XXX is UP.
neutron-
Now, in case this "local" ssh session gets realtime session status, I'd like to see it exported to an integrated tool like Prometheus :)
[1] https:/ /bugs.launchpad .net/neutron/ +bug/2023632