Skip to content

Add network exporter localprobe#12003

Draft
sven-rosenzweig wants to merge 4 commits into
masterfrom
add-network-exporter-localprobe
Draft

Add network exporter localprobe#12003
sven-rosenzweig wants to merge 4 commits into
masterfrom
add-network-exporter-localprobe

Conversation

@sven-rosenzweig

Copy link
Copy Markdown
Contributor

No description provided.

@sapcc-bot

Copy link
Copy Markdown
Contributor

Failed to validate the Prometheus rules. Details. Readme.

@sapcc-bot

Copy link
Copy Markdown
Contributor

Failed to validate the helm chart. Details. Readme.

@sven-rosenzweig sven-rosenzweig force-pushed the add-network-exporter-localprobe branch from 14055a2 to 72f81c1 Compare June 19, 2026 14:13
@sapcc-bot

Copy link
Copy Markdown
Contributor

Failed to validate the Prometheus rules. Details. Readme.

@sapcc-bot

Copy link
Copy Markdown
Contributor

Failed to validate the helm chart. Details. Readme.

@sven-rosenzweig sven-rosenzweig force-pushed the add-network-exporter-localprobe branch from 72f81c1 to 34534a8 Compare June 19, 2026 14:22
@sapcc-bot

Copy link
Copy Markdown
Contributor

Failed to validate the Prometheus rules. Details. Readme.

@sapcc-bot

Copy link
Copy Markdown
Contributor

Failed to validate the helm chart. Details. Readme.

Since we now have the network-node exporter and a picture of all subnets
with IP assignment from the DB we must not rely on the readiness probes
anymore. This will allow more granular alerting.
In the past this was done querying the neutron-api, asking for agents
assgigned to the agent and then comparing that to the netns/bridges
locally. This put some load on the api as we have a few dozen network
agents in each region, each asking the api for their networks.
With the network-node-exporter in place, we can also ask
prometheus-openstack for that information, shifting that load from the
neutron-api to prometheus, which pretty much already has that data lying
around.

I hope this
1) reduces our dependency to a slow neutron-api leading to failing
   readyness probes,
and
2) reduces the load generated though dozens of agents asking for their
   assigned networks.
@sven-rosenzweig sven-rosenzweig force-pushed the add-network-exporter-localprobe branch from 34534a8 to ea62f55 Compare June 23, 2026 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants