Skip to content

docs: record the telemetry identity fix reaching production - #143

Merged
kl3inIT merged 1 commit into
mainfrom
docs/record-telemetry-identity-applied
Jul 30, 2026
Merged

docs: record the telemetry identity fix reaching production#143
kl3inIT merged 1 commit into
mainfrom
docs/record-telemetry-identity-applied

Conversation

@kl3inIT

@kl3inIT kl3inIT commented Jul 30, 2026

Copy link
Copy Markdown
Owner

The plan carried this as an outstanding check: #140 fixed production's telemetry identity but the pipeline cannot deploy an infrastructure-only commit, so the fix sat merged and unapplied. It rode to the server with b4ea630.

Verified over SSH:

=== orgmemory-api-1 ===                    === orgmemory-worker-1 ===
image: …orgmemory-api:sha-b4ea630…           image: …orgmemory-worker:sha-b4ea630…
ORGMEMORY_SERVICE_VERSION=b4ea630…           ORGMEMORY_SERVICE_VERSION=b4ea630…
ORGMEMORY_DEPLOYMENT_ENVIRONMENT=production  ORGMEMORY_DEPLOYMENT_ENVIRONMENT=production

The version matches the tag of the image running it. That is the property the change existed to guarantee — pinning it in the same rewrite as the image tags is what makes drift impossible, and it is the failure a separate rewrite would have produced silently.

Phase 1's exporter silence held across the restart: zero publish failures, zero mentions of 4318, zero ERROR lines, no provider prompt-leak signatures in either service. The startup boundary verifier raised nothing against the real configuration.

Production previously labelled itself deployment.environment.name=local; it no longer does.

🤖 Generated with Claude Code

Verified on the ZM server after b4ea630 deployed. Both containers report the
production environment, and ORGMEMORY_SERVICE_VERSION holds exactly the commit
of the image running it — the property the single-rewrite change existed to
guarantee, and the one a separate rewrite could have broken silently.

Phase 1's exporter silence survived the restart, so this is the second
deployment with none of the warnings that opened the increment.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • docs/increments/active/2026-07-29-observability-pipeline/plan.md is excluded by !docs/**

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: df227cfb-bd38-4b50-88b3-f0c6494ed41a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@kl3inIT
kl3inIT merged commit 22234c9 into main Jul 30, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant