The opentelemetry PMDA is too strict when parsing input data (OTLP json) generated by a script or URL in config.d. The "strictness" is causing fail of the parser even on referential examples of OTLP json provided in OpenTelemetry specification.

Error messages in /var/log/pcp/pmcd/opentelemetry.log file are informing about failed parsing due to some missing fields in the OTLP json sample. For example:

Error: Error: Cannot refresh2 cluster 1: 'service_name'

is referring to missing resourceMetrics.resource.attributes.service_name field, however the specification is saying

 If the value was not specified, SDKs MUST fallback to "unknown_service:" concatenated with process.executable.name, e.g. "unknown_service:bash". If process.executable.name is not available, the value MUST be set to "unknown_service".

Another example is error

Error: Error: Cannot refresh2 cluster 1: 'description'

referring to missing description field of a metric. However the specification has this comment to the description field:

Users can provide a description, but it is up to their discretion. Therefore, the stream configuration parameter needs to be structured to accept a description, but MUST NOT obligate a user to provide one. If the user does not provide a description value, the description from the Instrument a View matches MUST be used by default.

Please provide the package NVR for which the bug is seen:

pcp-pmda-opentelemetry-7.0.3-1.el10

How reproducible is this bug?:

Always

Steps to reproduce

•  Try to parse referential examples of OTLP json provided in OpenTelemetry specification by the PMDA