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

agent: add ExtraIP per-VM metric #1292

Merged
merged 3 commits into from
Mar 7, 2025
Merged

agent: add ExtraIP per-VM metric #1292

merged 3 commits into from
Mar 7, 2025

Conversation

Omrigan
Copy link
Contributor

@Omrigan Omrigan commented Mar 3, 2025

Plus a couple of refactorings.

To be merged with rebase.

Part of #1294.

Copy link

github-actions bot commented Mar 3, 2025

No changes to the coverage.

HTML Report

Click to open

@Omrigan Omrigan changed the title agent: add extraIP per-VM metric agent: add ExtraIP per-VM metric Mar 3, 2025
@Omrigan Omrigan force-pushed the oleg/per-vm-metrics branch 2 times, most recently from 9bb5a3d to 3db7923 Compare March 6, 2025 11:51
@Omrigan Omrigan requested review from sharnoff and petuhovskiy March 6, 2025 21:46
Copy link
Member

@sharnoff sharnoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Refactorings seem mostly fair enough, one question.

re: Adding the metric — I wonder if we actually need this? What could you do with such a metric that you couldn't do before? (I'm imagining that you can always cross-reference with cplane's view of the VM if you want to check whether it has the overlay network enabled ­— but maybe I'm missing something!)

@Omrigan Omrigan force-pushed the oleg/per-vm-metrics branch 2 times, most recently from 673e799 to f36b9bb Compare March 7, 2025 11:58
@Omrigan
Copy link
Contributor Author

Omrigan commented Mar 7, 2025

Adding the metric — I wonder if we actually need this? What could you do with such a metric that you couldn't do before?

I thought of two use cases:

  1. View it in "per-VM metrics" dashboard, if we need to debug computes and network around it.
  2. Aggregate it to see the share of computes in the overlay network.

(I'm imagining that you can always cross-reference with cplane's view of the VM if you want to check whether it has the overlay network enabled ­— but maybe I'm missing something!)

Yeah, that's fair, but cplane info is not in grafana.

@Omrigan Omrigan assigned sharnoff and unassigned Omrigan Mar 7, 2025
Copy link
Member

@sharnoff sharnoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. A couple questions

@sharnoff sharnoff assigned Omrigan and unassigned sharnoff Mar 7, 2025
Omrigan added 3 commits March 7, 2025 14:31
Less chances for mistake.

Signed-off-by: Oleg Vasilev <[email protected]>
@Omrigan Omrigan force-pushed the oleg/per-vm-metrics branch from f36b9bb to 17a0e43 Compare March 7, 2025 14:31
@Omrigan Omrigan enabled auto-merge (rebase) March 7, 2025 14:58
@Omrigan Omrigan merged commit dd4b113 into main Mar 7, 2025
35 checks passed
@Omrigan Omrigan deleted the oleg/per-vm-metrics branch March 7, 2025 15:00
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.

2 participants