-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[receiver/splunkenterprise] Search Head Metrics #30263
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Pinging code owners for receiver/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/splunkenterprise
Is your feature request related to a problem? Please describe.
Currently metrics are focused primarily on Indexer instances. Adding Search Head specific metrics would be a good next set of signals.
Describe the solution you'd like
Additional metrics from the Search Head for things like skip ratio, report run times, scheduled search counts, scheduled search backlogs, etc
Ideally this work would be aligned with the issue for adding optional endpoint settings in the receiver to target specific kinds of splunk enterprise instances (search head, cluster manager, etc) #30254
Describe alternatives you've considered
These are additional sets of metrics, either they are worth adding and get added or they aren't. :)
Additional context
No response
The text was updated successfully, but these errors were encountered: