New component: Splunk Enterprise Receiver #12667
Comments
mx-psi
added
comp:splunk
|
I don't work on Splunk Enterprise, but I can sponsor this receiver |
|
Thank you @dmitryax. We have a few custom checks that existing with the SignalFx agent, however, I don't believe what we are doing is unique to just Atlassian so I am happy to upstream our work. |
What do you mean? Is there a Signalfx agent monitor for Spunk Enterprise? |
|
As in we've written a custom python monitor that currently monitors are hosted splunk platform using exposed rest endpoints that are published. (Sorry, still trying to wake up) |
|
Oh I see. Makes sense. It would be nice to have a native OTel collector receiver for that |
|
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 |
|
I'd be interested to see this one happen. How can I help? |
|
Hey @atoulme , Sorry, I've been meaning to come back to this one. What I wanted to do is take the existing internal python scripts we use to monitor splunk and upstream it for everyone to use. We are currently using Splunk 8 and looking forward to Splunk 9. What would be really helpful is any external documentation on monitor endpoints, associated runbooks, and potentially help validating if this could work with other deployments of Splunk would be amazing. |
|
Ah, I'm not sure I have a comprehensive guide. I'm always in favor of small iterations for this type of things - we can start with just one or two metrics. Splunk publishes an introspection API we can call: https://docs.splunk.com/Documentation/Splunk/9.0.1/RESTREF/RESTintrospect#server.2Fhealth.2Fdeployment Starting small with just one call. |
|
If you're happy to wait the weekend, my goal this week was to port our internal stuff to the collector to then share upstream. Also happy to talk more on slack |
|
No rush here. |
|
Happy new year! Interested if there's more to share now. |
|
I'm happy to work with @MovieStoreGuy on this |
|
I have somewhat of base PR made for this, but I haven't worked out the kinks in it. Let me open it up as a draft so that others can extend what I've done. |
|
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 |
|
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 |
|
@shalper2 are you planning to continue working on this? If so, can this be assigned to you? |
|
hey, yes sorry this should have been assigned to me! |
|
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 |
**Description:** First pass at implementing the component. This PR is primarily focused on implementing the components architecture with less focus on the collection of actual Splunk performance data. This was done to keep the PR relatively short. Considerable work has however been done to implement the receiver logic and accompanying tests. **Link to tracking Issue:** [12667](#12667)
**Description:** - Adds additional metrics to Splunk Enterprise receiver obtained from API endpoints - Updates tests and docs for these additional metrics **Link to tracking Issue:** #12667 **Testing:** - Additional tests for new endpoints and metrics added to `scraper_test` - Verify current tests also pass **Documentation:** - Newly generated docs entries for additional metrics
|
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 |
|
This is done! Closing as complete. |
) **Description:** - Adds additional metrics to Splunk Enterprise receiver obtained from API endpoints - Updates tests and docs for these additional metrics **Link to tracking Issue:** open-telemetry#12667 **Testing:** - Additional tests for new endpoints and metrics added to `scraper_test` - Verify current tests also pass **Documentation:** - Newly generated docs entries for additional metrics
The purpose and use-cases of the new component
For those using self host splunk (Splunk Enterprise), there is a few endpoints being exposed by the indexer cluster that can be captured and help monitor the platform.
Example configuration for the component
Telemetry data types supported
Metrics
Is this a vendor-specific component? If so, are you proposing to contribute this as a representative of the vendor?
This is a vendor specific component but I am happy for this component to be a community support receiver
Sponsor (Optional)
It would be nice to have someone from Splunk @dmitryax , @bogdandrutu as a sponsor for this.
The text was updated successfully, but these errors were encountered: