-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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] Configuration options for querying different enterprise instance types (SH, Indexer, Manager, etc) #30254
Comments
Pinging code owners for receiver/splunkenterprise: @shalper2 @MovieStoreGuy @greatestusername. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Removing |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
**Description:** Make changes to configuration of the application to allow the user to specify endpoints corresponding to different Splunk node types. Specifically, this update will allow users to define three separate clients: indexer, cluster master, and search head. This change will allow for the addition of metrics corresponding to these different modes of operation within the Splunk enterprise deployment. **Link to tracking Issue:** [30254](#30254) **Testing:** Unit tests were updated to run against new configuration options. **Documentation:** Updated README to reflect the new changes in configuration.
**Description:** Make changes to configuration of the application to allow the user to specify endpoints corresponding to different Splunk node types. Specifically, this update will allow users to define three separate clients: indexer, cluster master, and search head. This change will allow for the addition of metrics corresponding to these different modes of operation within the Splunk enterprise deployment. **Link to tracking Issue:** [30254](open-telemetry#30254) **Testing:** Unit tests were updated to run against new configuration options. **Documentation:** Updated README to reflect the new changes in configuration.
**Description:** Make changes to configuration of the application to allow the user to specify endpoints corresponding to different Splunk node types. Specifically, this update will allow users to define three separate clients: indexer, cluster master, and search head. This change will allow for the addition of metrics corresponding to these different modes of operation within the Splunk enterprise deployment. **Link to tracking Issue:** [30254](open-telemetry#30254) **Testing:** Unit tests were updated to run against new configuration options. **Documentation:** Updated README to reflect the new changes in configuration.
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/splunkenterprise
Is your feature request related to a problem? Please describe.
Some metrics require querying specifically a Search Head or specifically an Indexer (or a cluster manager, etc). Config currently only allows one endpoint that is expected to point at an Indexer and currently produces primarily Indexer metrics.
While possible to setup multiple receiver instances pointing at various instance types that would also require manually enabling/disabling the correct metrics for that instance type.
Describe the solution you'd like
Have optional configuration fields for different types of splunk enterprise instances that would then enable the metrics for that type of instance when applied. Essentially have optional fields for something like
indexer_endpoint
,search_head_endpoint
,cluster_manager_endpoint
and have metrics related to these specific instance types only be enabled when their instance type endpoint is defined.Describe alternatives you've considered
Possible to have multiple instances of the receiver, one for each type, but this is fiddly with enabling/disabling metrics.
Could allow a list of instances but would still require enabling/disabling metrics based on what instance types would be in the list
Additional context
Search head and cluster manager specific metrics will be added soon and this work would be a pre-requisite to adding those metrics.
The text was updated successfully, but these errors were encountered: