Infrastructure · llms.txt file breakdown
SigNoz organizes SigNoz content, including Starter docs, Agent tooling, API and access control, Optional.
The actual file
The saved llms.txt text, displayed as source. The file belongs to its publisher; the live endpoint may change.
Complete saved Markdown shown below.
# SigNoz
> SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry-native platform. Simple usage-based pricing, and the freedom to run on your infrastructure with Self-Hosted SigNoz.
Markdown versions of every page are available: append ".md" to any signoz.io page URL — docs (https://signoz.io/docs/introduction.md), blog posts (https://signoz.io/blog/<slug>.md), comparisons, guides, and product pages like https://signoz.io/pricing.md — or request any page with "Accept: text/markdown".
## Starter docs
- [Get Started](https://signoz.io/docs/introduction/): Learn about SigNoz, an open-source observability platform that helps you monitor your applications with distributed tracing, metrics, and logs.
- [Setup](https://signoz.io/docs/install/): Welcome to SigNoz! Send data from your application and infrastructure and get visibility into application performance within minutes.
- [SigNoz Cloud](https://signoz.io/docs/cloud/): SigNoz Cloud is a fully managed OpenTelemetry-native observability platform. Get started in minutes with unified APM, infrastructure monitoring, logs, and traces.
- [Collection Agents](https://signoz.io/docs/opentelemetry-collection-agents/get-started/): Overview of SigNoz collection agents for deploying and managing OpenTelemetry Collectors.
- [LLM Observability](https://signoz.io/docs/llm-observability/): Learn what LLM observability is and how to instrument LLM apps with OpenTelemetry. Trace token usage, latency, cost, and tool calls in SigNoz.
- [AWS Monitoring](https://signoz.io/docs/aws-monitoring/overview/): Discover supported AWS services like EC2, ECS, EKS, RDS, and Lambda. Compare one-click and manual OpenTelemetry integration methods to get started fast.
- [GCP Monitoring](https://signoz.io/docs/gcp-monitoring/): Monitor Google Cloud services in SigNoz including Cloud Functions, App Engine, Compute Engine, Cloud SQL, GKE, Cloud Run, and more.
- [Migrate to SigNoz](https://signoz.io/docs/migration/migrate-to-signoz/): Migrating from other observability vendors to SigNoz. How to migrate metrics, traces/APM, and logs to SigNoz.
- [From Datadog](https://signoz.io/docs/migration/migrate-from-datadog-to-signoz/): Complete guide to migrating from Datadog to SigNoz. How to migrate metrics, traces/APM, logs, dashboards, and alerts.
- [From Grafana Stack](https://signoz.io/docs/migration/migrate-from-grafana-to-signoz/): Comprehensive guide on migrating from the LGTM stack (Loki, Grafana, Tempo, Mimir) to SigNoz. Learn how to move your metrics, traces/APM, logs, and dashboards.
- [From ELK Stack](https://signoz.io/docs/migration/migrate-from-elk-to-signoz/): Learn how to migrate your metrics, traces/APM, logs, dashboards, and alerts from ELK Stack to SigNoz.
- [From New Relic](https://signoz.io/docs/migration/migrate-from-newrelic-to-signoz/): Learn how to migrate your metrics, traces/APM, logs, dashboards, and alerts from New Relic to SigNoz.
- [From Honeycomb](https://signoz.io/docs/migration/migrate-from-honeycomb-to-signoz/): Migrating from Honeycomb to SigNoz.
- [From OpenTelemetry](https://signoz.io/docs/migration/migrate-from-opentelemetry-to-signoz/): Migrating from OpenTelemetry to SigNoz. How to migrate metrics, traces/APM, and logs from OpenTelemetry to SigNoz.
- [From Self-Hosted to Cloud](https://signoz.io/docs/migration/migrate-from-signoz-self-host-to-signoz-cloud/): Step-by-step guide to migrate your observability setup from Self-Hosted SigNoz to SigNoz Cloud, including telemetry pipelines, dashboards, alerts, and pipelines.
- [APM & Distributed Tracing](https://signoz.io/docs/instrumentation/overview/): Learn how to set up APM (Application Performance Monitoring) and distributed tracing with SigNoz using OpenTelemetry. Instrument your app, visualize traces, and debug performance issues in minutes.
- [Debug Missing Data](https://signoz.io/docs/ingestion/signoz-cloud/troubleshooting/data-not-appearing/): Debug why your traces, logs, or metrics are not showing up in SigNoz, from SDK instrumentation to the OpenTelemetry Collector and the ingestion endpoint.
- [User Guides](https://signoz.io/docs/traces-management/guides/overview/): Guides for sampling trace volume, correlating traces with logs, scrubbing sensitive data, linking spans, and propagating trace context across services.
- [Metrics](https://signoz.io/docs/metrics-management/overview/): Collect and visualize numerical time-series data from applications and infrastructure in SigNoz.
- [Logs Management](https://signoz.io/docs/logs-management/overview/): Learn how SigNoz collects, searches, and analyzes logs using OpenTelemetry. Explore log sources, query tools, pipelines, and alerting.
- [Reference](https://signoz.io/docs/alerts-management/reference/): Reference documentation for alert evaluation patterns and time aggregation in SigNoz.
- [Dashboards](https://signoz.io/docs/dashboards/overview/): Build custom dashboards to visualize metrics, logs, and traces in SigNoz.
- [Administrator Guides](https://signoz.io/docs/manage/administrator-guide/): Learn how to manage SigNoz as an administrator
## Agent tooling
SigNoz ships Agent Skills and an MCP server so agents can read the docs and act on your observability data (query traces/logs/metrics, build dashboards, manage alerts). Install all skills: npx skills add SigNoz/agent-skills
- [Agent Skills & Plugin](https://signoz.io/docs/ai/agent-skills/): Install the SigNoz plugin and Agent Skills so AI agents like Claude Code, Codex, Cursor, and Gemini can query data, build dashboards, manage alerts, and explore SigNoz docs.
- [SigNoz MCP Server](https://signoz.io/docs/ai/signoz-mcp-server/): Connect Claude, Cursor, Copilot, and other AI agents to SigNoz via MCP for natural language access to metrics, logs, traces, and alerts.
- [AI Use Cases](https://signoz.io/docs/ai/use-cases/): Explore real-world AI workflows for debugging incidents, explaining dashboards, analyzing alerts, and reconstructing bugs with Noz and the SigNoz MCP Server.
- [skill.md](https://signoz.io/skill.md): Root Agent Skill file describing SigNoz skills and when the MCP server is required.
## API and access control
The SigNoz HTTP API authenticates with a SigNoz-Api-Key header; the OpenAPI document below declares the security schemes and every operation.
- [API reference](https://signoz.io/api-reference/): Interactive reference for the SigNoz HTTP API.
- [OpenAPI specification](https://signoz.io/api/api-reference-openapi/latest/): Machine-readable OpenAPI document for the SigNoz HTTP API, including security schemes.
- [Roles](https://signoz.io/docs/manage/administrator-guide/iam/roles/): Create and manage roles in SigNoz — managed roles, custom roles, and configuring transactions with the interactive or JSON editor.
- [Service Accounts](https://signoz.io/docs/manage/administrator-guide/iam/service-accounts/): Create and manage service accounts for programmatic API access in SigNoz
- [Self Service API Keys](https://signoz.io/docs/manage/administrator-guide/iam/user-guides/self-service-api-keys-for-viewers/): Let viewer users generate their own read-only API keys in SigNoz using a scoped custom role, assigned via invite or SSO group mapping.
- [Scope Telemetry Access](https://signoz.io/docs/manage/administrator-guide/iam/user-guides/scope-telemetry-access-by-ingestion-key/): Restrict a role to only the logs, traces, and metrics sent with a specific ingestion key in SigNoz using scoped telemetry transactions.
## Optional
- [Docs sitemap (markdown)](https://signoz.io/docs/sitemap.md): Markdown index of every SigNoz documentation page.
- [Blog & content sitemap (markdown)](https://signoz.io/blogs/sitemap.md): Markdown index of every blog post, guide, FAQ, case study, OpenTelemetry article, and comparison.
- [llms-full.txt](https://signoz.io/llms-full.txt): Entry-point map of all SigNoz content — docs, blog, product, alternatives, and company pages — with links to markdown sitemaps.
Measured from the saved file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
SigNoz Cloud brings your traces, metrics, and logs into one OpenTelemetry-native platform. Simple usage-based pricing, and the freedom to run on your infrastructure with Self-Hosted SigNoz.
Context architecture
4 H2 sections organize 36 parsed Markdown links. 3 links point to .md or .markdown paths; 0 link occurrences use another hostname. Linked destinations have not been recursively validated.
| H2 section | Links | UTF-8 bytes | Tokens |
|---|---|---|---|
| Starter docsLine 7 | 23 | 4567 | 1092 |
| Agent toolingLine 33 | 4 | 1015 | 250 |
| API and access controlLine 42 | 6 | 1322 | 297 |
| OptionalLine 53 · Optional | 3 | 473 | 119 |
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
1 H2 section named “Optional” contain 3 parsed links. 33 links sit outside those sections. That puts 8.3% of the file’s parsed links under Optional.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP-related text was detected in the captured file. 1 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
Index and bundle
Verified text companion
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
This capture establishes a baseline. Update frequency cannot be determined from one observation.
8 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
6ded2c52fe30a0d6c516665861840b0e1761668342fe7fc02e9a6eb512d8de14Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.