-
Notifications
You must be signed in to change notification settings - Fork 66
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
workload.googleapis.com/apache.current_connections
not available on all platforms
#1173
Comments
Would introducing the mechanism be a large effort? I'm not keen on removing existing coverage, especially for a really important metric like I'm not super familiar with apache; is the |
It's pretty easy to add a mechanism to skip certain platforms for specific metrics. I'd just add a platforms_to_skip field to expected_metrics in I looked into enabling |
+1 for introducing a mechanism to disable specific metrics on specific distros. Its possible this is something we encounter with other applications too and would be nice to have a mechanism to test metrics against what we expect for that distro. |
I'm working on enabling more test coverage for apache, and have found that
current_connections
is not available on centos-7, sles-12, or sles-15. I believe it's because that metric is specific to theevent
Multi-Processing Module (MPM), and isn't present on the other MPMs, which are used on older distros. Here's a snapshot of the apache server status page for various distros. Note that some of them are missingConnsTotal
:centos 7:
debian-11:
rocky-linux-8:
sles-15:
My question is, should we disable testing for the
current_connections
metric on all distros or introduce a mechanism to disable specific metrics on specific distros?The text was updated successfully, but these errors were encountered: