fix(pegboard): continue exporting metrics even if fetching actor fails

[NathanFlurry]

Changes

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat: db sh for workflows #2570
• fix(pegboard): fix enabling root users #2572
• fix(toolchain): fix compat with deploying using podman #2571
• feat: implement clickhouse-user-query #2554
• chore: add Linux ARM64 and Windows build targets #2551
• fix: uncomment function type filter in ACTORS_FILTER #2533
• chore(examples): multitenant deploys example #2527
• feat: add non-interactive mode and route management options to CLI #2532
• fix(pegboard): fix container runner orphaning #2575
• fix: dont include installing servers in service discovery #2569
• fix(pegboard): fix allocation metrics #2568
• fix: fix edge dc eligible calculation #2567
• fix(cluster): fix scaling logic and dedup metrics #2566
• feat(pegboard): add draining state to alloc metrics #2565
• fix(guard): dont route to installing api nodes #2564
• fix: improve error handling in status check #2563
• fix: add vector http config to edge configs #2553
• chore: fix dc wf #2552
• chore(vector): add vector pipeline to ship clickhouse events from the edge #2526
• fix(pegboard): increase actor log ttl to 14 days #2544
• feat(clusters): add margin per pool #2543
• Fix(guard): return error response on router error #2540
• fix(pegboard): wait for actor allocation not creation #2539
• fix(pegboard): increase signal timeout, add check for actor exit #2538
• fix(pegboard): revise actor rescheduling algorithm, add client metrics #2531
• fix: fix build cache key #2530
• feat: add retries to sql macros #2529
• fix: add create ts to server list #2523
• fix: fix pb metrics standalone #2518
• chore: disable OTEL by default in guard service #2522
• chore: increase file watch limit for rivet guard #2521
• fix(pegboard): continue exporting metrics even if fetching actor fails #2520 👈 (View in Graphite)
• fix(pegboard): fix collecting metrics for actors without workflows #2519
• feat(guard): add http ping endpoint to edge api hosts #2506
• chore: update workspace #2505
• chore: fix guard metrics #2504
• feat: add pb usage metrics, server state #2503
• fix(cache): add traces #2489
• fix(guard): add more tokio runtime metrics, remove labels from metrics #2485
• fix(guard): replace internal caches with moka #2481
• fix(guard): add metrics #2480
• chore: expose namespace in otel attributes #2501 : 1 other dependent PR (#2502 )
• chore: add standalone toolchain build scripts #2400 : 1 other dependent PR (#2500 )
• refactor: replace unsafe File::from_raw_fd with safe File::from #2479
• main

---

How to use the Graphite Merge Queue

Add 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.

[cloudflare-workers-and-pages]

Deploying rivet with    Cloudflare Pages

Latest commit:	3e0b88b
Status:	✅  Deploy successful!
Preview URL:	https://6e009397.rivet.pages.dev
Branch Preview URL:	https://05-31-fix-pegboard-continue.rivet.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying rivet-hub with    Cloudflare Pages

Latest commit:	3e0b88b
Status:	✅  Deploy successful!
Preview URL:	https://ae06cb93.rivet-hub-7jb.pages.dev
Branch Preview URL:	https://05-31-fix-pegboard-continue.rivet-hub-7jb.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying rivet-studio with    Cloudflare Pages

Latest commit:	3e0b88b
Status:	✅  Deploy successful!
Preview URL:	https://23f004ab.rivet-studio.pages.dev
Branch Preview URL:	https://05-31-fix-pegboard-continue.rivet-studio.pages.dev

View logs

[greptile-apps]

PR Summary

Enhances error handling in the pegboard metrics collection service to ensure continuous metrics export even when actor fetches fail. The changes introduce an allow_errors parameter across multiple components.

• Added allow_errors: true in pegboard/standalone/usage-metrics-publish/src/lib.rs to continue metrics collection despite actor fetch failures
• Implemented strict error handling (allow_errors: false) in actor API endpoints to maintain data integrity
• Added error handling logic in pegboard_actor_get operation to log warnings and continue processing when allow_errors is true
• Modified actor fetching stream to handle failures gracefully while maintaining metrics collection for available actors

_{4 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

style: Missing documentation for allow_errors field to explain when it should be used and potential implications.

Suggested change

	pub allow_errors: bool,
	/// When true, errors fetching individual actors will be logged and skipped instead of failing the entire operation.
	/// This is useful for bulk operations where partial failures are acceptable.
	pub allow_errors: bool,

[graphite-app]

Merge activity

• Jun 3, 7:01 AM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Jun 3, 7:02 AM UTC: CI is running for this pull request on a draft pull request (#2528) due to your merge queue CI optimization settings.
• Jun 3, 7:03 AM UTC: Merged by the Graphite merge queue via draft PR: #2528.