search

kumahq / kuma

🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.
https://kuma.io/install
Apache License 2.0
3.66k stars 333 forks source link

Metrics from ZoneIngress and ZoneEgress are not available #4348

Open lukidzi opened 2 years ago

lukidzi commented 2 years ago

What happened?

When Metrics are enabled in Grafana you can observe that metrics are available only for Dataplanes but not for ZoneEgress and ZoneIngress. It looks like while we are building listener for sidecars we only include Prometheus one to Dataplanes but not to ZoneEgress and ZoneIngress. Metrics configuration is Mesh specific, while ZoneEgress and ZoneIngress are Zone specific.

subnetmarco commented 2 years ago

We should probably have dedicated charts for these.

github-actions[bot] commented 2 years ago

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

github-actions[bot] commented 2 years ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

github-actions[bot] commented 1 year ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

lahabana commented 8 months ago

Expose it as a regular prometheus endpoint and scrape it outside of MeshMetric

github-actions[bot] commented 3 months ago

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.

lahabana commented 1 month ago

Should we use MeshMetric and filter stats based on the mesh? For otel I think that's quite feasible, for prometheus metrics maybe it would make sense to expose different endpoints?

What would happen to common stats? (like listeners for .e.g)