Adding a logical to a meter silently fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- matlab
- Domain
- observability-sre
Research direction
Start by reproducing the counter.add(logical(1)) and counter.add(double(logical(1))) calls shown in the issue, then query the /metrics endpoint with curl and compare the reported values. Trace the counter.add entry point to determine why the logical value has no effect, and verify that logical and converted numeric increments are reflected consistently in the metric.
Written by the indexing model from the issue text.
Description
Blot
Adding a logical to a meter will not increase the meter value, but also does not throw an error or warning. This isn't a timing issue in the example below, the collector had enough time to update between each increment of the meter and curl call below.
Example
>> m = opentelemetry.metrics.getMeter("test")
m =
Meter with properties:
Name: "test"
Version: ""
Schema: ""
>> counter = m.createCounter("mycounter")
counter =
Counter with properties:
Name: "mycounter"
Description: ""
Unit: ""
>> counter.add(3)
>> !curl -v http://localhost:8889/metrics
curl: /matlab/bin/glnxa64/libcurl.so.4: no version information available (required by curl)
* Host localhost:8889 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:8889...
* Connected to localhost (::1) port 8889
* using HTTP/1.x
> GET /metrics HTTP/1.1
> Host: localhost:8889
> User-Agent: curl/7.88.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Type: text/plain; version=0.0.4; charset=utf-8; escaping=underscores
< Date: Thu, 08 Jan 2026 20:43:02 GMT
< Content-Length: 190
< Connection: close
<
# HELP default_mycounter_total
# TYPE default_mycounter_total counter
default_mycounter_total{job="unknown_service",otel_scope_name="test",otel_scope_schema_url="",otel_scope_version=""} 3
* shutting down connection #0
>> counter.add(logical(1))
>> !curl -v http://localhost:8889/metrics
curl: /matlab/bin/glnxa64/libcurl.so.4: no version information available (required by curl)
* Host localhost:8889 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:8889...
* Connected to localhost (::1) port 8889
* using HTTP/1.x
> GET /metrics HTTP/1.1
> Host: localhost:8889
> User-Agent: curl/7.88.1
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/plain; version=0.0.4; charset=utf-8; escaping=underscores
< Date: Thu, 08 Jan 2026 20:46:11 GMT
< Content-Length: 190
< Connection: close
<
# HELP default_mycounter_total
# TYPE default_mycounter_total counter
default_mycounter_total{job="unknown_service",otel_scope_name="test",otel_scope_schema_url="",otel_scope_version=""} 3
* we are done reading and this is set to close, stop send
* abort upload
* shutting down connection #0
>> counter.add(double(logical(1)))
>> !curl -v http://localhost:8889/metrics
curl: /matlab/bin/glnxa64/libcurl.so.4: no version information available (required by curl)
* Host localhost:8889 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:8889...
* Connected to localhost (::1) port 8889
* using HTTP/1.x
> GET /metrics HTTP/1.1
> Host: localhost:8889
> User-Agent: curl/7.88.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Type: text/plain; version=0.0.4; charset=utf-8; escaping=underscores
< Date: Thu, 08 Jan 2026 20:51:06 GMT
< Content-Length: 190
< Connection: close
<
# HELP default_mycounter_total
# TYPE default_mycounter_total counter
default_mycounter_total{job="unknown_service",otel_scope_name="test",otel_scope_schema_url="",otel_scope_version=""} 4
* shutting down connection #0
- Dominant language
- MATLAB
- Stars
- 19
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mathworks/OpenTelemetry-MATLAB
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
documentation
mathworks/OpenTelemetry-MATLAB#248 · 1 assignee ·
-
test
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
otel-cpp changes
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
enhancement
mathworks/OpenTelemetry-MATLAB#242 · 1 comment · 1 assignee ·
All issues in mathworks/OpenTelemetry-MATLAB
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Documentation Good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
flatironinstitute/numbl#65 ·
-
Component: Continuous Integration Component: MATLAB Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100