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

wgengine/netstack: expose gVisor metrics through expvar #10899

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

andrew-d
Copy link
Member

When tailscaled is run with "-debug 127.0.0.1:12345", these metrics are available at:
http://localhost:12345/debug/metrics

Updates #8210

Change-Id: I19db6c445ac1f8344df2bc1066a3d9c9030606f8

When tailscaled is run with "-debug 127.0.0.1:12345", these metrics are
available at:
    http://localhost:12345/debug/metrics

Updates #8210

Signed-off-by: Andrew Dunham <andrew@du.nham.ca>
Change-Id: I19db6c445ac1f8344df2bc1066a3d9c9030606f8
Copy link
Contributor

@oxtoacart oxtoacart left a comment

Choose a reason for hiding this comment

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

LGTM, other than what appears to be an unrelated test failure.

@andrew-d andrew-d merged commit 7a0392a into main Jan 19, 2024
46 checks passed
@andrew-d andrew-d deleted the andrew/netstack-gvisor-metrics branch January 19, 2024 23:36
@knyar
Copy link
Contributor

knyar commented Feb 26, 2024

Is it deliberate that these metrics are only exposed via the local debug server and not via c2n?

@andrew-d
Copy link
Member Author

Is it deliberate that these metrics are only exposed via the local debug server and not via c2n?

Mostly, because it was a straightforward prototype. We do probably want to expose these in some other way, whether that be client metrics, C2N, or something else; I don't actually know what our current recommended approach is for metrics collection.

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.

None yet

3 participants