From c95b03c7311c3322125302e520f898e7bb73b9c2 Mon Sep 17 00:00:00 2001 From: Yuri Shkuro Date: Fri, 10 Jan 2025 16:15:04 -0500 Subject: [PATCH] Specify admin endpoints Signed-off-by: Yuri Shkuro --- content/docs/2.2/deployment.md | 14 +++++++------- content/docs/next-release-v2/deployment.md | 14 +++++++------- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/content/docs/2.2/deployment.md b/content/docs/2.2/deployment.md index 74df0ece..40234223 100644 --- a/content/docs/2.2/deployment.md +++ b/content/docs/2.2/deployment.md @@ -20,18 +20,18 @@ Jaeger backend is released as a single binary or container image (see [Downloads The following intra-oriented ports are exposed by default (can be changed via configuration): -Port | Protocol | Function ------ | ------- | --- -8888 | HTTP | metrics port for exposing metrics which can be scraped with Prometheus compatible systems at `/metrics` -8889 | HTTP | ingester port for reading data from Kafka topics and writing to a supported backend -13133 | HTTP | Healthcheck port via the `healthcheckv2` extension -27777 | HTTP | expvar port for process level metrics per the Go standards +Port | Protocol | Endpoint | Function +----- | ------- | ---------- | -------- +8888 | HTTP | `/metrics` | metrics port for exposing metrics which can be scraped with Prometheus compatible systems +8889 | HTTP | `/metrics` | ingester port for reading data from Kafka topics and writing to a supported backend +13133 | HTTP | `/status` | Healthcheck port via the `healthcheckv2` extension +27777 | HTTP | `/` | expvar port for process level metrics per the Go standards See [APIs](../apis/) for the list of all API ports. ## Configuration -Jaeger can be customized via configuration YAML file (see [Configuration](../configuration/)). +Jaeger can be customized via configuration YAML file (see [Configuration](../configuration/)). Jaeger **collector** is stateless and thus many instances of **collector** can be run in parallel. **collector** instances require almost no configuration, except for storage location, such as [Cassandra](../cassandra/#configuration) or [Elasticsearch](../elasticsearch/#configuration). diff --git a/content/docs/next-release-v2/deployment.md b/content/docs/next-release-v2/deployment.md index 74df0ece..40234223 100644 --- a/content/docs/next-release-v2/deployment.md +++ b/content/docs/next-release-v2/deployment.md @@ -20,18 +20,18 @@ Jaeger backend is released as a single binary or container image (see [Downloads The following intra-oriented ports are exposed by default (can be changed via configuration): -Port | Protocol | Function ------ | ------- | --- -8888 | HTTP | metrics port for exposing metrics which can be scraped with Prometheus compatible systems at `/metrics` -8889 | HTTP | ingester port for reading data from Kafka topics and writing to a supported backend -13133 | HTTP | Healthcheck port via the `healthcheckv2` extension -27777 | HTTP | expvar port for process level metrics per the Go standards +Port | Protocol | Endpoint | Function +----- | ------- | ---------- | -------- +8888 | HTTP | `/metrics` | metrics port for exposing metrics which can be scraped with Prometheus compatible systems +8889 | HTTP | `/metrics` | ingester port for reading data from Kafka topics and writing to a supported backend +13133 | HTTP | `/status` | Healthcheck port via the `healthcheckv2` extension +27777 | HTTP | `/` | expvar port for process level metrics per the Go standards See [APIs](../apis/) for the list of all API ports. ## Configuration -Jaeger can be customized via configuration YAML file (see [Configuration](../configuration/)). +Jaeger can be customized via configuration YAML file (see [Configuration](../configuration/)). Jaeger **collector** is stateless and thus many instances of **collector** can be run in parallel. **collector** instances require almost no configuration, except for storage location, such as [Cassandra](../cassandra/#configuration) or [Elasticsearch](../elasticsearch/#configuration).