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] Adding Telemetry around KV Store #35445

Open
michael-burt opened this issue Sep 26, 2024 · 3 comments
Open

[receiver/splunkenterprise] Adding Telemetry around KV Store #35445

michael-burt opened this issue Sep 26, 2024 · 3 comments
Labels

Comments

@michael-burt
Copy link

Component(s)

receiver/splunkenterprise

Is your feature request related to a problem? Please describe.

Currently, the Splunk Enterprise Receiver lacks the ability to report on the status of KV Store, KV Store replication, and KV Store backups. This information can be gathered from the /services/kvstore/status API endpoint in Splunk.

Describe the solution you'd like

I would like to add metrics around the KV Store to splunkenterprisereceiver.

Describe alternatives you've considered

No response

Additional context

No response

@michael-burt michael-burt added enhancement New feature or request needs triage New item requiring triage labels Sep 26, 2024
@michael-burt michael-burt changed the title [receiver/splunkenterprise] [receiver/splunkenterprise] Adding Telemetry around KV Store Sep 26, 2024
Copy link
Contributor

Pinging code owners:

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

@shalper2
Copy link
Contributor

I think this would be a great addition to the receiver and I’d be happy to work on it.

@crobert-1
Copy link
Member

Removing needs triage based on response from code owner.

@crobert-1 crobert-1 removed the needs triage New item requiring triage label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants