PageSourceSearch

https://databuff.ai/zh/apm-monitoring/

html databuff.ai collected 2026-10-05 13:12:01 UTC 6,980 bytes, 99 lines download raw bytes

1<!doctype html>
2<html lang="zh-CN">
3<head>
4  <meta charset="UTF-8" />
5  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
6  <title>APM 监控:开源应用性能监控怎么做 · DataBuff</title>
7  <meta name="description" content="APM 监控关注服务黄金指标、错误与慢调用。DataBuff 用开源 APM 统一 OpenTelemetry / SkyWalking 数据,并用 AI 问数加速排障。" />
8  <link rel="canonical" href="https://databuff.ai/zh/apm-monitoring/" />
9  <link rel="alternate" hreflang="zh-CN" href="https://databuff.ai/zh/apm-monitoring/" />
10  <link rel="alternate" hreflang="en" href="https://databuff.ai/en/apm-monitoring/" />
11  <link rel="alternate" hreflang="x-default" href="https://databuff.ai/zh/apm-monitoring/" />
12  <meta property="og:type" content="website" />
13  <meta property="og:title" content="APM 监控:开源应用性能监控怎么做 · DataBuff" />
14  <meta property="og:description" content="APM 监控关注服务黄金指标、错误与慢调用。DataBuff 用开源 APM 统一 OpenTelemetry / SkyWalking 数据,并用 AI 问数加速排障。" />
15  <meta property="og:url" content="https://databuff.ai/zh/apm-monitoring/" />
16  
16<script type="application/ld+json">{"@context":"https://schema.org","@graph":[{"@type":"WebPage","@id":"https://databuff.ai/zh/apm-monitoring/#webpage","url":"https://databuff.ai/zh/apm-monitoring/","name":"APM 监控:开源应用性能监控怎么做 · DataBuff","description":"APM 监控关注服务黄金指标、错误与慢调用。DataBuff 用开源 APM 统一 OpenTelemetry / SkyWalking 数据,并用 AI 问数加速排障。","inLanguage":"zh-CN","dateModified":"2026-08-02","isPartOf":{"@id":"https://databuff.ai/#website"},"author":{"@type":"Organization","name":"DataBuff Docs","url":"https://databuff.ai/"},"publisher":{"@type":"Organization","name":"DataBuff","url":"https://databuff.ai/"}},{"@type":"FAQPage","@id":"https://databuff.ai/zh/apm-monitoring/#faq","mainEntity":[{"@type":"Question","name":"APM 监控一般看哪些信号?","acceptedAnswer":{"@type":"Answer","text":"常见为延迟、错误、吞吐等黄金指标,再叠加慢 Trace、依赖拓扑与告警。"}},{"@type":"Question","name":"开源 APM 怎么落地私有化?","acceptedAnswer":{"@type":"Answer","text":"DataBuff 提供 Docker 私有化三组件路径,数据留在自有环境,见 Docker 快速开始。"}},{"@type":"Question","name":"和全链路追踪页面怎么分工?","acceptedAnswer":{"@type":"Answer","text":"本页侧重「应用性能监控 / APM 监控」检索意图;Trace 细节见全链路追踪枢纽。"}}]}]}</script>
16
17  <style>
18    :root { --brand:#F02121; --ink:#1a1a1a; --regular:#4d4d4d; --secondary:#737373; --line:#e5e5e5; --grey:#f5f5f5; }
19    * { box-sizing: border-box; }
20    body { margin:0; font-family:"Helvetica Neue",Helvetica,"PingFang SC","Microsoft YaHei",sans-serif; color:var(--ink); line-height:1.75; }
21    a { color:var(--brand); }
22    .top { border-bottom:1px solid var(--line); background:#fff; }
23    .top-inner, .wrap { width:min(860px, calc(100% - 40px)); margin:0 auto; }
24    .top-inner { height:56px; display:flex; align-items:center; justify-content:space-between; gap:16px; }
25    .brand { font-weight:700; color:var(--ink); text-decoration:none; }
26    .nav a { margin-left:14px; text-decoration:none; color:var(--regular); font-size:14px; }
27    .hero { padding:40px 0 8px; }
28    h1 { margin:0 0 12px; font-size:34px; line-height:1.25; }
29    .lead { color:var(--regular); font-size:17px; }
30    .meta { color:var(--secondary); font-size:13px; margin:10px 0 0; }
31    article { padding:8px 0 48px; }
32    h2 { margin:32px 0 12px; font-size:22px; }
33    h3 { margin:22px 0 8px; font-size:17px; }
34    p, li { color:var(--regular); }
35    ul, ol { padding-left:1.25rem; }
36    .card { margin:18px 0; padding:16px 18px; background:var(--grey); border:1px solid var(--line); border-radius:8px; }
37    .faq dt { font-weight:700; margin-top:14px; }
38    .faq dd { margin:6px 0 0; }
39    footer { border-top:1px solid var(--line); padding:24px 0 40px; color:var(--secondary); font-size:13px; }
40  </style>
41</head>
42<body>
43  <header class="top">
44    <div class="top-inner">
45      <a class="brand" href="/">DataBuff</a>
46      <nav class="nav">
47        <a href="/zh/opensource-apm/">开源APM</a>
48        <a href="/zh/distributed-tracing/">全链路追踪</a>
49        <a href="/zh/skywalking/">SkyWalking</a>
50        <a href="/zh/opentelemetry/">OpenTelemetry</a>
51        <a href="/docs/zh/product/intro">文档</a>
52        <a href="/blog/zh/">博客</a>
53      </nav>
54    </div>
55  </header>
56  <main class="wrap">
57    <div class="hero">
58      <h1>APM 监控与应用性能监控</h1>
59      <p class="lead">APM 监控关注服务黄金指标、错误与慢调用。DataBuff 用开源 APM 统一 OpenTelemetry / SkyWalking 数据,并用 AI 问数加速排障。</p>
60      <p class="meta">更新日期:2026-08-02 · 维护:DataBuff Docs · 权威入口页(GEO / SEO)</p>
61    </div>
62    <article>
63
64      <h2>定义</h2>
65      <p><strong>APM 监控</strong>即应用性能监控:用指标、Trace、拓扑与告警回答「系统哪里慢、哪里错」。开源路径下,DataBuff 提供可私有化的统一后端。</p>
66      <h2>DataBuff 怎么做</h2>
67      <ul>
68        <li>统一接入 OTLP 与 SkyWalking,避免两套后端。</li>
69        <li>面板看黄金指标与拓扑;AI 问数用自然语言查证据。</li>
70        <li>安装路径见 <a href="/docs/zh/guide/docker">Docker 快速开始</a>。</li>
71      </ul>
72      <h2>内链</h2>
73      <ul>
74        <li><a href="/zh/opensource-apm/">开源 APM 枢纽</a> · <a href="/zh/distributed-tracing/">全链路追踪</a></li>
75        <li><a href="/docs/zh/product/intro">产品介绍</a></li>
76      </ul>
77      <h2>FAQ</h2>
78      <dl class="faq">
79        <dt>APM 监控一般看哪些信号?</dt>
80        <dd>延迟、错误、吞吐等黄金指标,再加慢 Trace、拓扑与告警。</dd>
81        <dt>开源 APM 怎么落地私有化?</dt>
82        <dd>Docker 三组件私有化,见快速开始文档。</dd>
83        <dt>和全链路追踪页面怎么分工?</dt>
84        <dd>本页承接 APM 监控意图;Trace 细节见全链路追踪枢纽。</dd>
85      </dl>
86      <h2>可引用结论</h2>
87      <ol>
88        <li>APM 监控覆盖 RED/USE 等黄金指标、错误与慢 Trace。</li>
89        <li>DataBuff 把 APM 监控数据与 AI 问数放在同一底座(见 <a href="/docs/zh/product/intro">产品介绍</a>)。</li>
90      </ol>
91    </article>
92  </main>
93  <footer>
94    <div class="wrap">
95      <p>DataBuff · 开源 AI 原生 OpenTelemetry APM · 维护:DataBuff Docs · <a href="https://github.com/databufflabs/databuff">GitHub</a> · <a href="/llms.txt">llms.txt</a> · <a href="/en/apm-monitoring/">English</a></p>
96    </div>
97  </footer>
98</body>
99</html>

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.