We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This issue was created based on a discussion about #176.
General guidelines for metric instrumentation units require that for measuring durations, seconds should be used:
When instruments are measuring durations, seconds (i.e. s) SHOULD be used.
However, the following FaaS metrics still use milliseconds for measuring durations:
faas.invoke_duration
faas.init_duration
faas.cpu.usage
Those metrics don't seem to be implemented currently, so changes can be done without a OTEL_SEMCONV_STABILITY_OPT_IN compatibility mechanism.
OTEL_SEMCONV_STABILITY_OPT_IN
The text was updated successfully, but these errors were encountered:
arminru
Successfully merging a pull request may close this issue.
This issue was created based on a discussion about #176.
General guidelines for metric instrumentation units require that for measuring durations, seconds should be used:
However, the following FaaS metrics still use milliseconds for measuring durations:
faas.invoke_duration
faas.init_duration
faas.cpu.usage
Those metrics don't seem to be implemented currently, so changes can be done without a
OTEL_SEMCONV_STABILITY_OPT_IN
compatibility mechanism.The text was updated successfully, but these errors were encountered: