docs(platform): observability & in-product data architecture design record - #656
Open
rigel-mintaka wants to merge 1 commit into
Open
docs(platform): observability & in-product data architecture design record#656rigel-mintaka wants to merge 1 commit into
rigel-mintaka wants to merge 1 commit into
Conversation
rigel-mintaka
changed the title
rigel-mintaka
force-pushed
the
compass-agent/obs-architecture-design
branch
from
August 26, 2026 16:57
20ab7a2 to
a5e3b18
Compare
rigel-mintaka
changed the title
rigel-mintaka
force-pushed
the
compass-agent/obs-architecture-design
branch
from
August 26, 2026 16:59
a5e3b18 to
1e1f16d
Compare
|
Compass engineering docs preview: https://compass-agent-obs-architectu.compass-eng-docs.pages.dev Deployed from Changed pages: |
rigel-mintaka
force-pushed
the
compass-agent/obs-architecture-design
branch
from
August 26, 2026 21:45
1e1f16d to
fd43d95
Compare
…ecord Full observability architecture for Compass: the in-product data surface (Plane A, native Solid charts from the server's own store), the OTLP ops export + fan-in collector (Plane B), and both crossed with the two products (self-hosted core vs managed multi-tenant). Resolves the data store question as Decision D1 via a three-data-class analysis: in-product usage/spend is bounded per-org Postgres; the ops firehose lives on the external LGTM backend; cross-tenant analytics is private-plane OLAP. No bigger dep for the core. Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
force-pushed
the
compass-agent/obs-architecture-design
branch
from
August 26, 2026 22:55
fd43d95 to
c6badc9
Compare
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
1 participant
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.
Full observability architecture for Compass: the in-product data surface
(Plane A, native Solid charts from the server's own store), the OTLP ops
export + fan-in collector (Plane B), and both crossed with the two
products (self-hosted core vs managed multi-tenant). Resolves the data
store question as Decision D1 via a three-data-class analysis: in-product
usage/spend is bounded per-org Postgres; the ops firehose lives on the
external LGTM backend; cross-tenant analytics is private-plane OLAP. No
bigger dep for the core.
Co-authored-by: Matt Wilkinson matt@rigel.build