signoz-docs

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use official

signoz.io

documentation and API references only. Ground every answer in fetched docs content and cite the canonical docs URL.

仅使用官方

signoz.io

文档和API参考。所有回答都必须基于获取的文档内容，并引用标准文档URL。

SigNoz docs support

Accept: text/markdown

. Fetch docs pages as markdown instead of scraping HTML.

SigNoz文档支持

Accept: text/markdown

。请以markdown格式获取文档页面，而非抓取HTML。

Use the sitemap to search for candidate pages:

GET https://signoz.io/docs/sitemap.md

使用站点地图搜索候选页面：

GET https://signoz.io/docs/sitemap.md

Fetch any docs page as markdown by requesting it with:

GET https://signoz.io/docs/<path>/
Accept: text/markdown

For example, to fetch the logs overview page:

GET https://signoz.io/docs/logs-management/overview/
Accept: text/markdown

通过以下请求以markdown格式获取任意文档页面：

GET https://signoz.io/docs/<path>/
Accept: text/markdown

例如，获取日志概览页面：

GET https://signoz.io/docs/logs-management/overview/
Accept: text/markdown

Identify the domain from the user's question: instrumentation, OpenTelemetry setup, querying, dashboards, alerts, troubleshooting, deployment, or API docs.
Check the heuristics table below. If a heuristic matches, read that file before choosing docs pages.
Search
sitemap.md
for candidate pages that match the user's product area, environment, language, and task.
Rank the best 2-5 official pages by how directly they help the user complete the task.
Fetch only the top page(s) as markdown with
```
Accept: text/markdown
```
.
- Fetch one page for narrow questions that map cleanly to a single setup guide, troubleshooting page, or API reference.
- Fetch multiple pages when the task clearly spans multiple needs, such as collection-method selection plus a language guide, setup plus troubleshooting, or overview plus exact API/auth details.
- Keep the fetch set small and purposeful. Do not fetch loosely related pages just because they share keywords.
Answer from the fetched docs and cite canonical
```
https://signoz.io/docs/...
```
URLs.
Handle ambiguity deliberately: if multiple pages are plausible, prefer the page that completes the task most directly and mention alternates only when they materially change the answer.

Prefer setup, troubleshooting, or API-reference pages over overview pages when the user needs an action.
Prefer pages that match the user's runtime, language, deployment environment, or SigNoz product area.
For API questions, prefer the exact endpoint/auth/reference page over a general guide.
Stay within official
```
signoz.io
```
docs pages when this skill applies.

Read the matching heuristic file before fetching docs. Each file contains decision logic to route the user to the right guide.

Topic	Trigger keywords	Heuristic file
Sending Logs	logs, log collection, logging, send logs	sending-logs.md

在获取文档前，请先阅读匹配的启发式规则文件。每个文件包含决策逻辑，可将用户引导至正确的指南。

主题	触发关键词	启发式规则文件
发送日志	logs, log collection, logging, send logs	sending-logs.md