-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Add Metrics Around Search Performance #39566
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
Labels
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
MovieStoreGuy
added a commit
that referenced
this issue
Apr 29, 2025
…iver (#39569) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Added a new `splunk.search.initiation`, `splunk.search.duration`, `splunk.search.status`, and `splunk.search.success` metrics. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #39566 <!--Describe what testing was performed and which tests were added.--> #### Testing Ran on a test stack and observed the metrics in Splunk Observability  <!--Describe the documentation added.--> #### Documentation The only documentation added was the generated documentation about the newly added metrics. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Sean Marciniak <[email protected]>
vincentfree
pushed a commit
to ing-bank/opentelemetry-collector-contrib
that referenced
this issue
May 6, 2025
…iver (open-telemetry#39569) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Added a new `splunk.search.initiation`, `splunk.search.duration`, `splunk.search.status`, and `splunk.search.success` metrics. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#39566 <!--Describe what testing was performed and which tests were added.--> #### Testing Ran on a test stack and observed the metrics in Splunk Observability  <!--Describe the documentation added.--> #### Documentation The only documentation added was the generated documentation about the newly added metrics. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Sean Marciniak <[email protected]>
vincentfree
pushed a commit
to ing-bank/opentelemetry-collector-contrib
that referenced
this issue
May 20, 2025
…iver (open-telemetry#39569) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Added a new `splunk.search.initiation`, `splunk.search.duration`, `splunk.search.status`, and `splunk.search.success` metrics. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#39566 <!--Describe what testing was performed and which tests were added.--> #### Testing Ran on a test stack and observed the metrics in Splunk Observability  <!--Describe the documentation added.--> #### Documentation The only documentation added was the generated documentation about the newly added metrics. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Sean Marciniak <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component(s)
receiver/splunkenterprise
Is your feature request related to a problem? Please describe.
I want general metrics around the performance of a simple search on my system.
Describe the solution you'd like
I would like to know if searches can be initiated, whether they succeed, how long they take, and what state the search may be in in order to properly monitor how search is performing on my system.
Describe alternatives you've considered
The splunkenterprisereceiver does not currently receive metrics of this nature.
Additional context
No response
The text was updated successfully, but these errors were encountered: