See user macros with context for more information. New templates Etcd • Template App Etcd by HTTP - collects metrics from Etcd’s /metrics endpoint with HTTP agent (see description). Microsoft SQL Zabbix agent 2. Changes in 5.0.2 New templates are available: • Template App Etcd by HTTP - collects metrics from Etcd’s /metrics endpoint with HTTP agent (see description). • Template DB MSSQL by ODBC Template App Etcd by HTTP {$ETCD.PORT}- the port used by Etcd API endpoint (default: 2379). {$ETCD.SCHEME} - the request scheme. Supported: http (default), https. {$ETCD.USER}, {$ETCD.PASSWORD} -

expression"} 使用正则表达式可以显著减少需要定义的用户宏上下文的数量。 点击带有上下文的用户宏 查看更多信息. 新的模板 526 Etcd 模板 • Template App Etcd by HTTP - 通过 HTTP 代理从 Etcd’s /metrics 中收集监控指标数据 (点击 查看说明). Microsoft SQL Server 模板 • Template DB MSSQL Zabbix agent 2. Changes in 5.0.2 New templates are available: • Template App Etcd by HTTP - collects metrics from Etcd’s /metrics endpoint with HTTP agent (see description). • Template DB MSSQL by ODBC Template App Etcd by HTTP {$ETCD.PORT} - Etcd API 端点的端口号 (默认： 2379). 度量数据被从 AP{$ETCD.SCHEME} - 请求协 议，支持：http (默认), https. {$ETCD.USER}, {$ETCD.PASSWORD} - 登录凭据, 仅 当用于 Etcd 身份验证时才需要。检验 Etcd 是否被配置允 许本 端

authentication. - Etcd by HTTP {$ETCD.PORT}- the port used by Etcd API endpoint (default: 2379). {$ETCD.SCHEME} - the request scheme. Supported: http (default), https. {$ETCD.USER}, {$ETCD.PASSWORD} - required only if used for Etcd authentication. Metrics are collected from /metrics endpoint; to specify the endpoint’s location use --listen-metrics-urls flag (see Etcd documentation for details). whether Etcd is configured to allow metric collection, run: curl -L http://localhost:2379/metrics To check, if Etcd is accessible from Zabbix proxy or Zabbix server run: curl -L http:%%//<etcd_node_a

steps/comments Etcd by HTTP {$ETCD.PORT}- the port used by Etcd API endpoint (default: 2379). {$ETCD.SCHEME} - the request scheme. Supported: http (default), https. {$ETCD.USER}, {$ETCD.PASSWORD} - required only if used for Etcd authentication. Metrics are collected from /metrics endpoint; to specify the endpoint’s location use --listen-metrics-urls flag (see Etcd documentation for details). whether Etcd is configured to allow metric collection, run: curl -L http://localhost:2379/metrics To check, if Etcd is accessible from Zabbix proxy or Zabbix server run: curl -L http:%%//<etcd_node_a

steps/comments Etcd by HTTP {$ETCD.PORT}- the port used by Etcd API endpoint (default: 2379). {$ETCD.SCHEME} - the request scheme. Supported: http (default), https. {$ETCD.USER}, {$ETCD.PASSWORD} - required only if used for Etcd authentication. Metrics are collected from /metrics endpoint; to specify the endpoint’s location use --listen-metrics-urls flag (see Etcd documentation for details). whether Etcd is configured to allow metric collection, run: curl -L http://localhost:2379/metrics To check, if Etcd is accessible from Zabbix proxy or Zabbix server run: curl -L http:%%//<etcd_node_a

424 模板 必配宏 附加步骤/注释 Etcd by HTTP {$ETCD.PORT}- Etcd API 端点的端口 号 (默认: 2379). {$ETCD.SCHEME} - 请求协议. 支持: http (默认), https. {$ETCD.USER}, {$ETCD.PASSWORD} - 登陆凭证, 仅 当用于 Etcd 身份验证时才需要. 端点的接口路径/metrics 参数 (详情参见 Etcd 文档). 本地验证 Etcd 指标采集，执行: curl -L http://localhost:2379/metrics 检查 Etcd 指标可以从 Zabbix proxy 或 Zabbix server 采集，执 行: curl -L http:%%//<etcd_node_adress>:2379/metrics%% 每个 Etcd 的节点都需要链接这个模板

exposes metrics in Prometheus line format, including Kubernetes, Docker, GitLab, Ceph, Collectd, etcd, InfluxDB, InfluxDB Telegraf and others. Zabbix uses HTTP items to access Prometheus metrics and

by HTTP • DELL PowerEdge R840 by HTTP • Elasticsearch Cluster by HTTP • Envoy Proxy by HTTP • Etcd by HTTP • GitLab by HTTP • Hadoop by HTTP • HAProxy by HTTP • HashiCorp Consul Cluster by HTTP

by HTTP • DELL PowerEdge R840 by HTTP • Elasticsearch Cluster by HTTP • Envoy Proxy by HTTP • Etcd by HTTP 446 • FortiGate by HTTP • GitLab by HTTP • Google Cloud Platform by HTTP (GCP by HTTP)

HTTP • DELL PowerEdge R840 by HTTP • Elasticsearch Cluster by HTTP • Envoy Proxy by HTTP 389 • Etcd by HTTP • FortiGate by HTTP • GitLab by HTTP • Google Cloud Platform (GCP) by HTTP • Hadoop by