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

1.  Install pcp-zeroconf, pcp-pmda-opentelemetry and register the pcp-pmda-opentelemetry

   dnf -y install pcp-zeroconf pcp-pmda-opentelemetry && cd /var/lib/pcp/pmdas/opentelemetry && ./Install
   

1.  Create a script which always fails

   echo -e '#!/bin/sh\nexit 1' > /var/lib/pcp/pmdas/opentelemetry/config.d/errscript && chmod +x /var/lib/pcp/pmdas/opentelemetry/config.d/errscript
   

1.  Trigger the script execution

   pminfo -f opentelemetry
   

Expected results

The opentelemetry.control.status_code will provide non zero value for the errscript instance.

Actual results

The opentelemetry.control.status_code always provides zero value for instances representing scripts.

Note

The man page of the pmdaopentelemetry PMDA provides description only for URL data sources. Description for scripted data sources is missing for the opentelemetry.control.status_code metric. However my expectation is that the status_code will reflect somehow non zero exit code of the data source script. Please update the man page with expected behavior of the opentelemetry.control.status_code metric on a scripted data source. Also, if my expectation is correct, please fix the status_code value for failing scripted data sources.