Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitoring metrics do not report external BGP peers #848

Open
salanki opened this issue Feb 29, 2020 · 1 comment
Open

Monitoring metrics do not report external BGP peers #848

salanki opened this issue Feb 29, 2020 · 1 comment
Labels
enhancement override-stale Don't allow automatic management of stale issues / PRs
Milestone

Comments

@salanki
Copy link

salanki commented Feb 29, 2020

The Prometheus metric kube_router_controller_bgp_peers does not include eBGP peers. Some setups, ie. when peering with a ToR switch this is the only type of peer that is used. Monitoring proper function is impossible in these setups.

As the node can be in Ready state even with 0 BGP peers traffic from any pod scheduled on a node without the peer established will be blackholed, leading to service interruptions.

I'd suggest either including eBGP peers in the kube_router_controller_bgp_peers count, or adding a separate metric for it.

It would also make sense to add an option signal the CNI as NonReady until a peer has been established.

@murali-reddy
Copy link
Member

@salanki thanks for suggestion. I am marking the bug for backlog of improvements.

@aauren aauren added the override-stale Don't allow automatic management of stale issues / PRs label Sep 4, 2023
@aauren aauren added this to the v2.1.0 milestone Jan 6, 2024
@aauren aauren modified the milestones: v2.1.0, v2.2.0 Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement override-stale Don't allow automatic management of stale issues / PRs
Projects
None yet
Development

No branches or pull requests

3 participants