| 2023-09-06 08:43:14 |
Nishant Dash |
description |
- When I configure this example federate job through the charm config `federate-config`,
```
- job_name: 'mesh-federate'
scrape_interval: 2m
scrape_timeout: 1m
honor_labels: true
metrics_path: '/federate'
params:
'match[]':
- '{__name__=~".+"}'
static_configs:
- targets:
- '<FQDN of other prometheus server>:9090'
```
- The job does not show up.
In the Prometheus UI -> Status -> Configuration, I see
```
- job_name: mesh-federate
honor_labels: true
honor_timestamps: true
params:
match[]:
- '{__name__=~".+"}'
scrape_interval: 15s
scrape_timeout: 15s
metrics_path: /federate
scheme: http
follow_redirects: true
enable_http2: true
static_configs:
- targets: []
labels:
group: promoagents-federate
```
As such, the target is missing and the scrape interval and timeout seem to be from the charm configs `scrape-timeout` and `scrape-interval` instead. |
- When I configure this example federate job through the charm config `federate-config`,
```
- job_name: 'mesh-federate'
scrape_interval: 2m
scrape_timeout: 1m
honor_labels: true
metrics_path: '/federate'
params:
'match[]':
- '{__name__=~".+"}'
static_configs:
- targets:
- '<FQDN of other prometheus server>:9090'
```
- The job does not show up.
In the Prometheus UI -> Status -> Configuration, I see
```
- job_name: mesh-federate
honor_labels: true
honor_timestamps: true
params:
match[]:
- '{__name__=~".+"}'
scrape_interval: 15s
scrape_timeout: 15s
metrics_path: /federate
scheme: http
follow_redirects: true
enable_http2: true
static_configs:
- targets: []
labels:
group: promoagents-federate
```
As such, the target is missing and the scrape interval and timeout seem to be from the charm configs `scrape-timeout` and `scrape-interval` instead.
This charm is stable, 48. |
|
