BM-3054: docs(ops-logs-query): point prover log groups at new boundless/hlc/prover groups - #2041
Draft
willpote wants to merge 2 commits into
Draft
BM-3054: docs(ops-logs-query): point prover log groups at new boundless/hlc/prover groups#2041willpote wants to merge 2 commits into
willpote wants to merge 2 commits into
Conversation
…over groups Reflect the consolidated two-prover model (prover-prod / prover-staging, each in its own AWS account) shipping to boundless/hlc/prover. Document the per-account message envelope, the staging broker-log shipping gap, and move the old /boundless/bento/prover-* groups to a legacy section. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…log groups Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the
ops-logs-queryskill to reflect the consolidated two-prover model that went live on 2026-06-08. Both provers now ship to a log group literally namedboundless/hlc/prover(one per AWS account), with a single stream each.[aws.prod])boundless/hlc/proverprover-prod[aws.staging])boundless/hlc/proverprover-stagingChanges
/boundless/bento/prover-*table with the newboundless/hlc/provermodel (account → stream → role).{"message":...}; staging: wrapped{"host","identifier","unit",...}) and thejqparse idiom.prover-stagingstream ships onlybento_cliagent stdout underdocker.service— broker module logs and kernel messages are not reaching CloudWatch. Treat absence-of-broker-logs on staging as a monitoring gap, not an idle broker.BPLatitudeRelease/Nightly,prover-01/02, testnet variants) to a "legacy / decommissioned" table (stopped shipping 2026-05-29).Verification
prover-prodcarries full broker logs and ~10k fulfillments / 24h.prover-stagingcurrently ships onlybento_cli/docker.service(the documented gap).🤖 Generated with Claude Code