-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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] 35445 add kvstore telemetry #35657
[receiver/splunkenterprise] 35445 add kvstore telemetry #35657
Conversation
f9f8678
to
c869f33
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me!
Open question: Any other attributes that might be useful? instance id/guid or some other identifier?
You could apply those as part of the resource or attribute processor, if you have any recommend values I would suggest adding it as an example configuration in the README :) |
Are you able to add any tests to help validate that this works as expected? |
4c50fad
to
edf070f
Compare
5bddfc7
to
3d61fad
Compare
Any chance we can mark this as ready to merge? |
There is a required test that is failing, we cannot merge until that is fixed |
Aaah sorry forgot to |
3d61fad
to
5d80f1d
Compare
@mx-psi should be all good to go now! |
5d80f1d
to
b32d82c
Compare
…ry#35657) #### Description Add telemetry around KV Store status to the Splunk Enterprise Receiver. #### Link to tracking issue Fixes [35445](open-telemetry#35445) #### Testing Unit tests were updated and receiver component was deployed to test environments. #### Documentation Documentation was updated to reflect additional metrics
Description
Add telemetry around KV Store status to the Splunk Enterprise Receiver.
Link to tracking issue
Fixes 35445
Testing
Unit tests were updated and receiver component was deployed to test environments.
Documentation
Documentation was updated to reflect additional metrics