Add the LGTM stack and Integrations overview pages - #416
Merged
Conversation
|
@stakater-user Image is available for testing. |
|
@aayeshaarshad Image is available for testing. |
msafwankarim
added
the
screenshots-captured
|
@aayeshaarshad PR doc deploy will soon be available for review on https://stakater.github.io/mto-docs/docs-lgtm-stack |
|
@aayeshaarshad Image is available for testing. |
Add an overview page to the Integrations section
|
@aayeshaarshad PR doc deploy will soon be available for review on https://stakater.github.io/mto-docs/docs-lgtm-stack |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
@aayeshaarshad Image is available for testing. |
aayeshaarshad
changed the title
rasheedamir
approved these changes
Aug 13, 2026
|
@rasheedamir PR doc deploy was successfully deleted from branch pull-request-deployments |
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
3 participants
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.
Adds two pages to the Integrations section, and the nav entries for both.
The LGTM stack page
content/integrations/lgtm/lgtm.mddocuments multi-tenant observability acrossthe whole stack: how telemetry is collected per tenant, and what enforces the
tenant boundary in front of each component. It complements the Grafana
integration page rather than repeating it — Grafana's own surface
(organisations, data sources, dashboards, sign-in) is linked, not restated.
Structure: what a tenant gets, what you do not have to configure per tenant,
how it works (architecture diagram, ingestion, what settles the tenant), what
the stack is made of, and what can be tailored.
Claims were checked against the upstream docs and our repositories:
X-Scope-OrgIDand noneauthenticates it; all three upstream docs direct you to an authenticating
reverse proxy and make that proxy responsible for setting the header.
mto-loki-gateway and mto-mimir-gateway READMEs and middleware.
Prometheus needs a block per tenant; the Template Operator renders those
from the
Tenantlist.operator and chart; Grafana publishes no Mimir operator; Grafana must come
from the Grafana Operator; Tempo's authenticating gateway is the operator's,
the chart's nginx gateway only does basic auth.
The Integrations overview page
content/integrations/overview.mdcame in via #417, which was merged into thisbranch rather than into
main. This PR is therefore what carries it tomain.It is the section index, and it links the LGTM page, so the two belong together.
Note: that page lists six integrations but omits OpenBao, which is now in the
nav — it was written before #413 landed.
Checks
Vale passes on both pages. The nav lists overview, ArgoCD, Grafana, LGTM,
Vault, OpenBao, DevWorkspace and Mattermost.