-
Notifications
You must be signed in to change notification settings - Fork 129
chore: change otel collector policies #2436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
How to use the Graphite Merge QueueAdd the label merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
Modified OpenTelemetry Collector configuration in cluster service to replace latency-based sampling with targeted OTTL condition-based sampling policies.
- Changed sampling in
/packages/core/services/cluster/src/workflows/server/install/install_scripts/files/otel_collector.shto focus on specific span events ('subscribe' and 'message') with 'pegboard_actor_ready' attribute - Removed latency-based sampling (>15s) for 'routing_fn' spans which may impact visibility of slow operations
- Added ERROR status code sampling policy to ensure error traces are captured
- Configured tail sampling with 60s decision wait time and 50,000 trace buffer
1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile
| - name: policy-2 | ||
| type: and | ||
| and: | ||
| and_sub_policy: | ||
| - name: latency-policy-1 | ||
| type: latency | ||
| latency: | ||
| threshold_ms: 15000 | ||
| - name: span-name-policy-1 | ||
| type: ottl_condition | ||
| ottl_condition: | ||
| span: | ||
| - 'name == "routing_fn"' | ||
| type: ottl_condition | ||
| ottl_condition: | ||
| span: | ||
| - 'name == "subscribe" and attributes["message"] == "pegboard_actor_ready"' | ||
| - name: policy-3 | ||
| type: ottl_condition | ||
| ottl_condition: | ||
| span: | ||
| - 'name == "message" and attributes["message"] == "pegboard_actor_ready"' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
style: Policies 2 and 3 appear to be sampling for identical conditions (pegboard_actor_ready) with only slightly different span names. Consider consolidating these into a single policy with an OR condition.
f17b27a to
21b246a
Compare
Deploying rivet with
|
| Latest commit: |
3c8db79
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://24dd18a4.rivet.pages.dev |
| Branch Preview URL: | https://05-10-chore-change-otel-coll.rivet.pages.dev |
21b246a to
3c8db79
Compare
3c8db79 to
56647b9
Compare
Merge activity
|
<!-- Please make sure there is an issue that this PR is correlated to. --> ## Changes <!-- If there are frontend changes, please include screenshots. -->

Changes