| 2021-01-13 02:16:27 |
Seyeong Kim |
bug |
|
|
added bug |
| 2021-01-13 03:25:04 |
Seyeong Kim |
tags |
|
sts |
|
| 2021-01-26 16:15:13 |
George Kraft |
charm-kubernetes-master: importance |
Undecided |
High |
|
| 2021-01-26 16:15:15 |
George Kraft |
charm-kubernetes-master: status |
New |
Triaged |
|
| 2021-01-29 02:02:09 |
Seyeong Kim |
description |
For now, In prometheus UI, I can't see scheduler_ prefixed metrics.
I've analyzed this a few and found out kubernetes-master doesn't register manual_job for kube-scheduler
so I added template manually like below
##
scrape_interval: 30s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- 10.0.0.9:10251 ( kubernetes-master/leader 's ipaddress )
##
then I can see scheduler_ prefixed metrics in prometheus UI.
It would be better if there is way to export kube-scheduler's metrics as well.
Thanks. |
For now, In prometheus UI, I can't see scheduler_ prefixed metrics.
I've analyzed this a few and found out kubernetes-master doesn't register manual_job for kube-scheduler
so I added template manually like below
##
scrape_interval: 30s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- 10.0.0.9:10251 ( kubernetes-master/leader 's ipaddress )
##
then I can see scheduler_ prefixed metrics in prometheus UI.
It would be better if there is way to export kube-scheduler's metrics as well.
ADDED
In addition to kube-scheduler, kube-controller-manager and kube-proxy metrics also not exported to prometheus.
Thanks. |
|
| 2021-01-29 02:02:17 |
Seyeong Kim |
summary |
Metrics from kube-scheduler need to be exported to prometheus charm |
Metrics from kube-scheduler, kube-controller-manager and kube-proxy need to be exported to prometheus charm |
|
| 2021-02-03 02:53:58 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
| 2021-03-05 02:16:47 |
Seyeong Kim |
description |
For now, In prometheus UI, I can't see scheduler_ prefixed metrics.
I've analyzed this a few and found out kubernetes-master doesn't register manual_job for kube-scheduler
so I added template manually like below
##
scrape_interval: 30s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- 10.0.0.9:10251 ( kubernetes-master/leader 's ipaddress )
##
then I can see scheduler_ prefixed metrics in prometheus UI.
It would be better if there is way to export kube-scheduler's metrics as well.
ADDED
In addition to kube-scheduler, kube-controller-manager and kube-proxy metrics also not exported to prometheus.
Thanks. |
For now, In prometheus UI, I can't see scheduler_ prefixed metrics.
I've analyzed this a few and found out kubernetes-master doesn't register manual_job for kube-scheduler
so I added template manually like below
##
scrape_interval: 30s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- 10.0.0.9:10251 ( kubernetes-master/leader 's ipaddress )
##
then I can see scheduler_ prefixed metrics in prometheus UI.
It would be better if there is way to export kube-scheduler's metrics as well.
ADDED
In addition to kube-scheduler, kube-controller-manager and kube-proxy metrics also not exported to prometheus.
For kube-proxy, kube-proxy snap need to be changed as it doesn't export it's metric for now.
--metrics-bind-address ipport Default: 127.0.0.1:10249 ( https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ )
Thanks. |
|
| 2021-04-15 05:42:08 |
Seyeong Kim |
description |
For now, In prometheus UI, I can't see scheduler_ prefixed metrics.
I've analyzed this a few and found out kubernetes-master doesn't register manual_job for kube-scheduler
so I added template manually like below
##
scrape_interval: 30s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- 10.0.0.9:10251 ( kubernetes-master/leader 's ipaddress )
##
then I can see scheduler_ prefixed metrics in prometheus UI.
It would be better if there is way to export kube-scheduler's metrics as well.
ADDED
In addition to kube-scheduler, kube-controller-manager and kube-proxy metrics also not exported to prometheus.
For kube-proxy, kube-proxy snap need to be changed as it doesn't export it's metric for now.
--metrics-bind-address ipport Default: 127.0.0.1:10249 ( https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ )
Thanks. |
For now, In prometheus UI, I can't see scheduler_ prefixed metrics.
I've analyzed this a few and found out kubernetes-master doesn't register manual_job for kube-scheduler
so I added template manually like below
##
scrape_interval: 30s
metrics_path: /metrics
scheme: http
static_configs:
- targets:
- 10.0.0.9:10251 ( kubernetes-master/leader 's ipaddress )
##
then I can see scheduler_ prefixed metrics in prometheus UI.
It would be better if there is way to export kube-scheduler's metrics as well.
ADDED
In addition to kube-scheduler, kube-controller-manager and kube-proxy metrics also not exported to prometheus.
For kube-proxy, kube-proxy snap need to be changed as it doesn't export it's metric for now.
--metrics-bind-address ipport Default: 127.0.0.1:10249 ( https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ )
ADDED for @cynerva's
Just adding template can't solve this issue as
e.g kube-state-metrics exposed by using service & endpoint with k8s deployment ( for kube-state-metrics)
So it can be access with metrics_path: /api/v1/namespaces/kube-system/services/kube-state-metrics:8081/proxy/metrics
But for kube-scheduler, kube-controller-manager, kube-proxy are not exposed.
I tried to create service & endpoint for kube-scheduler, but it is local service inside k8s-master unit not deployment.
I think we need to change deployment structure to expose those.
Please give me some more advice or please engage canonical k8s team for this.
Thanks. |
|
| 2021-06-14 20:26:55 |
Paul Goins |
bug |
|
|
added subscriber alive-shad (BootStack) |
