[BUG] Monitoring is broken in 1.0.112 (latest version)
Status Fixed / completed
Maintainer reply None cached
Activity 9 comments · opened Sep 12, 2025 · closed Sep 12, 2025
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Claude Code Opentelemetry feature is broken.
Broken means it does not produce any logs / metrics.
It does not produce metrics / logs even after we configure that.
What Should Happen?
After we configure the telemetry setting, the claude code should produce metrics / logs.
Error Messages/Logs
No error messages found.Steps to Reproduce
~/.claude/settings.json
{
"env": {
"AWS_PROFILE": "<AWS ROLE>",
"AWS_REGION": "<AWS REGION>",
"NODE_TLS_REJECT_UNAUTHORIZED": 0,
"ANTHROPIC_SMALL_FAST_MODEL_AWS_REGION": "<AWS REGION>",
"CLAUDE_CODE_USE_BEDROCK": 1,
"ANTHROPIC_MODEL": "<Model Inference Profile ID>",
"ANTHROPIC_SMALL_FAST_MODEL": "<Model Inference Profile ID>",
"ANTHROPIC_CUSTOM_HEADERS": "X-Amzn-Bedrock-GuardrailIdentifier: <GuardrailID>\nX-Amzn-Bedrock-GuardrailVersion: <GuardrailVersion>",
"CLAUDE_CODE_ENABLE_TELEMETRY": 1,
"OTEL_METRICS_EXPORTER": "console",
"OTEL_METRIC_EXPORT_INTERVAL": 1000,
"OTEL_METRICS_INCLUDE_SESSION_ID": false,
"OTEL_RESOURCE_ATTRIBUTES": "user.name=testuser"
}
}Claude Model
Other
Is this a regression?
Yes, this worked in a previous version
Last Working Version
1.0.110
Claude Code Version
1.0.112
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
9 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Other issues you mentioned were due to mis configuration. This one is real issue because we've been using this without any issue until 1.0.110 but it suddenly appeared after upgrading to 1.0.111 and above.
+1, seeing this same issue. This was working and suddenly stopped since I have auto update on
Also confirmed that monitoring still works when forcing version to
1.0.110Confirmed. Rolled back to 1.0.110 and it started working again.
Thank you for reporting this issue. To help with the investigation, can someone confirm if it works when they set the env variable through bash instead of using
~/.claude/settings.json?May I know why this issue has been closed?
@kushal-thakkar
Hi sorry for the confusion. I have merged a fix and it should be available in the next release on Monday.
Thanks!
Confirms it's been fixed in 1.0.115
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.