metricsname includes a "-" which is not a valid metrics name

[thel1988]

Metricsname includes a "-" which is not a valid metrics name

According to the documentation from splunk putting a "-" in the metrics name is not valid.
https://help.splunk.com/en/splunk-enterprise/get-data-in/metrics/9.4/introduction-to-metrics/overview-of-metrics

As we have put Splunk OTEL collector in between splunk-connect-for-snmp and Splunk Enterprise, it currently does not support: "-" according to: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/fab70b831af2303a9eba7a8d52db3792957c30e0/internal/splunk/common.go

Currently sc4snmp is sending the var-binds directly with: "-" which produces an example like:

{
    "event": "metric",
    "time": "1751875553",
    "index": "netmetrics",
    "host": "testserver.console.test.example:161",
    "sourcetype": "sc4snmp:metric",
    "source": "sc4snmpv7",   
    "fields": {
        "group": "dell_idracs",
        "metric_name:sc4snmp.IDRAC-MIB-SMIv2.memoryDeviceTableEntry": 3.0,
        "mibIndex": "28.1.4"
        }
}

The IDRAC-MIB-SMIv2 is not correct according to Splunk documentation should be underscores: "_" instead

I know it works directly to Splunk, but either documentation above should be corrected or this behaviour should be corrected.

[omrozowicz-splunk]

Thanks for raising this! We agree it's a valid point. We're actively working on a parameterized solution to address this, ensuring it doesn't impact existing customer dashboards not using OTel. A PR is already open and this feature will be included in the upcoming beta.

[omrozowicz-splunk]

Hello @thel1988,
the beta version with a fix was released within #1213, this is also included within the newest 1.13.0-beta.5. If you're okay with using beta versions you can upgrade it according to this doc. This change require to add a parameter according to the documentation released for now on documentation for beta.