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

[receiver/splunkenterprise] Search Head Metrics #30263

Closed
greatestusername-splunk opened this issue Jan 2, 2024 · 4 comments
Closed

[receiver/splunkenterprise] Search Head Metrics #30263

greatestusername-splunk opened this issue Jan 2, 2024 · 4 comments

Comments

@greatestusername-splunk
Copy link

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

@greatestusername-splunk greatestusername-splunk added enhancement New feature or request needs triage New item requiring triage labels Jan 2, 2024
Copy link
Contributor

github-actions bot commented Jan 2, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

github-actions bot commented Jan 2, 2024

Pinging code owners for receiver/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername. See Adding Labels via Comments if you do not have permissions to add labels yourself.

@crobert-1 crobert-1 removed the needs triage New item requiring triage label Jan 2, 2024
Copy link
Contributor

github-actions bot commented Mar 4, 2024

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Mar 4, 2024
Copy link
Contributor

github-actions bot commented May 3, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants