Skip to content

docs(use-cases): self-host an AI agent observability backend on-prem - #588

Open
CodeStaple wants to merge 1 commit into
masterfrom
docs/self-host-ai-agent-observability
Open

CodeStaple wants to merge 1 commit into
masterfrom
docs/self-host-ai-agent-observability

Conversation

@CodeStaple

Copy link
Copy Markdown
Contributor

What

A new use case, Self-host an AI agent observability backend on-prem (use-cases/self-host-ai-agent-observability.mdx), written for the platform engineers of Moyai's customers. It covers what runs (diagram), prerequisites, install with a dry run, secret files and one deploy, the LLM choice (in-cluster CPU demo, your own vLLM, or an OpenAI-compatible API), verification, upgrades with stack-profiles rollout, and air-gapped notes.

Also:

  • images/use-cases/self-host-ai-agent-observability.svg, in the house diagram style with light and dark themes
  • docs.json: the page joins the Use Cases group
  • changelog.mdx: one 2026-10-19 entry

Why

Moyai publishes its backend as a private stack profile, moyai-observatory, and shares it with its customers' Ankra organisations so they can run it on Proxmox, HPE Morpheus, an imported cluster or any cloud. This page shows that path and how short it is. The parameter names on the page are the ones in the published profile, and the commands were checked against it with apply --dry-run.

The repo is public, so the page names no Moyai cluster, hostname, registry path or id.

Checks

  • scripts/check_nav.py, check_frontmatter.py, check_snippets.py, check_changelog.py: OK
  • mint broken-links: no broken links
  • Rendered with mint dev: the page, its tabs and the /concepts/stack-profiles#share-with-specific-organisations anchor resolve
  • No em dashes

Bead: ankra-s05q7l

🤖 Generated with Claude Code

A use case for Moyai's customers' platform engineers: apply the shared
moyai-observatory stack profile (easterisland API, CloudNativePG Postgres
HA, SeaweedFS S3, Lakekeeper Iceberg REST catalog, LLM, Prometheus) to
any Ankra cluster, choose the LLM, verify, upgrade with rollout, and run
it air-gapped. Adds the diagram, the nav entry and a changelog entry.

Bead: ankra-s05q7l

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ankra-platform

ankra-platform Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

✅ Run #236 succeeded

Run #236 for commit f2efc3e (pull request #588).

Stage Step Outcome Duration
build build success 1m 31s
checkout checkout success 39s
gate gate success 0s
publish publish skipped -
scan scan (tool=checkov) success 1m 30s
scan scan (tool=semgrep) success 41s
scan scan (tool=trivy) success 1m 3s

Open this run in Ankra

🔗 Details ↗ · Updated Oct 19, 2026, 10:38 AM UTC


Ankra AI review

Verdict: looks good.

Docs-only PR adding a new use-case page, a changelog entry, a nav entry in docs.json, and an SVG diagram. Content is internally consistent: CLI commands, input names, and secret-file bindings match between the install and upgrade sections, and sensible security guidance (umask 077, SOPS-sealed secrets, warning against otel_dev_mode on shared clusters) is included. No correctness, security, or pipeline issues found in the diff itself; CI is still running, so build status is unknown but the change is low-risk.


Reviewed commit f2efc3e. This review is read-only and advisory.

@ankra-platform

ankra-platform Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

This Ankra AI review comment was superseded: two review turns for this pull request overlapped, and the other one holds the review thread. The current review is the other Ankra AI review comment on this pull request, and its footer names the commit it covers.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant