[receiver/splunkenterprise] fix flaky search for iops metrics #35081
Comments
shalper2
added
bug
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Makes sense to me, and was filed by a code owner. Removing |
…35082) **Description:** Quick bugfix for a flaky Splunk search related to gathering average iops metrics in the splunkenterprise receiver. **Link to tracking Issue:** [35081](#35081) **Testing:** Tested amended search in splunk enterprise deployments and received proper results **Documentation:** no new documentation provided --------- Co-authored-by: Curtis Robert <[email protected]>
…pen-telemetry#35082) **Description:** Quick bugfix for a flaky Splunk search related to gathering average iops metrics in the splunkenterprise receiver. **Link to tracking Issue:** [35081](open-telemetry#35081) **Testing:** Tested amended search in splunk enterprise deployments and received proper results **Documentation:** no new documentation provided --------- Co-authored-by: Curtis Robert <[email protected]>
|
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
What happened?
Description
The search which generates the iops metrics is flaky due to a reference to a directory which may not be present on the Splunk deployment's host machine.
Collector version
v0.108.0
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
This is not an issue directly related to the opentelemetry collector or even the splunkenterprise receiver's own internal logic/implementation.
The text was updated successfully, but these errors were encountered: