AmerDwight commented on issue #10721:
URL: https://github.com/apache/apisix/issues/10721#issuecomment-1870723873
Yes, thank you. The endpoint now can provide some data for me.
**But, I can't catch the upstream status in prometheus still.**
The metric that provides to prometheus now only contains:
```
apisix_bandwidth
apisix_etcd_modify_indexes
apisix_etcd_reachable
apisix_http_latency_bucket
apisix_http_latency_count
apisix_http_latency_sum
apisix_http_request_total
apisix_http_status
apisix_nginx_http_current_connections
apisix_nginx_metric_errors_total
apisix_node_info
apisix_shared_dict_capacity_bytes
apisix_shared_dict_free_space_bytes
```
no "**apisix_upstream_status**" or something similar
Is there anything I missed?
**config of prometheus**
```yml
global:
scrape_interval: 1s # By default, scrape targets every 15 seconds.
evaluation_interval: 20s
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
stack: "apisix"
rule_files:
- "rules.yml"
alerting:
alertmanagers:
- scheme: http
static_configs:
- targets: [ 'alert_manager:9093' ]
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
# The job name is added as a label `job=<job_name>` to any timeseries
scraped from this config.
- job_name: "prometheus"
# Override the global default and scrape targets from this job every 5
seconds.
scrape_interval: 5s
static_configs:
- targets: ["localhost:9090"]
- job_name: "apisix"
scrape_interval: 5s
metrics_path: "/apisix/prometheus/metrics"
static_configs:
- targets: ["apisix:9091"]
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
