Reduce OpenTelemetry ingestion volume - #2414
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2bc894e46e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 443f6ac1cd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4c5f28fa96
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| error_mode: ignore | ||
| traces: | ||
| span: | ||
| - 'attributes["db.system"] == "redis" and status.code != STATUS_CODE_ERROR and (resource.attributes["service.name"] == "exceptionless-web" or resource.attributes["service.name"] == "job-event-posts")' |
There was a problem hiding this comment.
Restore the prefixed event-post service matcher
Fresh evidence after the prior thread is that fb99bd9 reverted 12111d8's correction in the reviewed target tree. The production job loads Apm.ServiceName: exceptionless from src/Exceptionless.Job/appsettings.yml, while Program.cs passes job-event-posts to ApmConfig, whose concatenation emits service.name=exceptionless-job-event-posts; therefore successful Redis spans from this high-volume worker never match this predicate and continue to both exporters. Restore the prefixed matcher.
Useful? React with 👍 / 👎.
Summary
http.server.request.durationhistogram buckets at the .NET SDKMessage: EntityChangedspans globallyk8s-infrachart from 0.15.0 to 0.16.0 and migrate SigNoz Cloud export from OTLP/gRPC to OTLP/HTTPImpact
This reduces metric-series and trace-span ingestion volume before export to SigNoz and Elastic. The metric drop policy remains in Collector configuration, so it can be changed through a Collector deployment without rebuilding the applications. The applications still generate and send these metrics to their node Collector.
Other messaging spans remain unchanged.
Dependency upgrade
signoz/k8s-infra0.15.0 → 0.16.0otel/opentelemetry-collector-contrib:0.139.0Version 0.16.0 changes the default SigNoz exporter from OTLP/gRPC to OTLP/HTTP. This change explicitly enables only
otlphttp, adds the requiredhttps://endpoint scheme, and updates the custom pipeline exporter lists. The separate Elastic gRPC exporter is unchanged. GitHub listed no published security advisories forSigNoz/chartsat the time of review.Validation
k8s-infra0.16.0 with Collector 0.139.0signoz/k8s-infra0.16.0 chart with Helm 4.2.0 and the proposed valuesbatchotlphttpexporter, the existingotlp/elasticexporter, and both filters beforebatchMessage: EntityChangedand successfulexceptionless-webRedis spansservice.name=job-event-postsk8s/signoz.yamlas YAMLdotnet build src/Exceptionless.Web/Exceptionless.Web.csproj --maxcpucount:1 --no-restoredotnet build src/Exceptionless.Job/Exceptionless.Job.csproj --maxcpucount:1 --no-restoregit diff --checkBoth .NET builds completed with zero warnings and zero errors.
Deployment note
The Collector chart is deployed separately from the Exceptionless applications. Apply the updated Collector values for the strict metric filter and corrected event-post service matcher. Only the histogram bucket change requires deploying application images containing this PR.