open-telemetry / open-telemetry/opentelemetry-python-contrib

system.memory.usage has no temporality and type being sent

Open
#2,857 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug instrumentation metrics
Dominant language
Python
Stars
1.1k
Forks
1.1k
Avg merge
4d 15h
Merged PRs (30d)
16

Description

Describe your environment

OS: (e.g, Ubuntu)
Python version: (e.g., Python 3.8.10)
Package version: (e.g., 0.46.0)

What happened?

system.memory.usage has no temporality and type being sent, should it be standardize as the receiver https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/hostmetricsreceiver/internal/scraper/memoryscraper/documentation.md?

Steps to Reproduce

metric_exporter = OTLPMetricExporter(endpoint="xxx", max_export_batch_size=512)
set_meter_provider(MeterProvider([PeriodicExportingMetricReader(metric_exporter), PeriodicExportingMetricReader(ConsoleMetricExporter())], resource=resource))
SystemMetricsInstrumentor().instrument()

Expected Result

My dashboard expecting those 2 column to be filled.

Actual Result

temporality = 'Unspecified', type = 'Gauge'

Additional context

No response

Would you like to implement a fix?

None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with SystemMetricsInstrumentor and the system.memory.usage metric produced by the provided OTLPMetricExporter example. Compare its temporality and type with the hostmetrics receiver memory scraper documentation, then rerun the reproduction and verify both fields are populated as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.