You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**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.
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: 'enhancement'
5
+
6
+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7
+
component: splunkentreceiver
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: "Updated the config.go and propogated these changes to other receiver components. Change was necessary to differentiate different configurable endpoints."
11
+
12
+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13
+
issues: [30254]
14
+
15
+
# (Optional) One or more lines of additional information to render under the primary note.
16
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17
+
# Use pipe (|) for multiline entries.
18
+
subtext:
19
+
20
+
# If your change doesn't affect end users or the exported elements of any package,
21
+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22
+
# Optional: The change log or logs in which this entry should be included.
23
+
# e.g. '[user]' or '[user, api]'
24
+
# Include 'user' if the change is relevant to end users.
25
+
# Include 'api' if there is a change to a library API.
Copy file name to clipboardExpand all lines: receiver/splunkenterprisereceiver/README.md
+29-5Lines changed: 29 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,9 @@ jobs.
8
8
9
9
## Configuration
10
10
11
-
The following settings are required, omitting them will either cause your receiver to fail to compile or result in 4/5xx return codes during scraping.
11
+
The following settings are required, omitting them will either cause your receiver to fail to compile or result in 4/5xx return codes during scraping.
12
+
13
+
**NOTE:** These must be set for each Splunk instance type (indexer, search head, or cluster master) from which you wish to pull metrics. At present, only one of each type is accepted, per configured receiver instance. This means, for example, that if you have three different "indexer" type instances that you would like to pull metrics from you will need to configure three different `splunkenterprise` receivers for each indexer node you wish to monitor.
12
14
13
15
*`basicauth` (from [basicauthextension](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/basicauthextension)): A configured stanza for the basicauthextension.
14
16
*`auth` (no default): String name referencing your auth extension.
0 commit comments