Replies: 2 comments
-
The metrics you are pasted here are coming from the Strimzi operator. They are not Kafka metrics. |
Beta Was this translation helpful? Give feedback.
-
What do you mean with Prometheus Exporter Pod? The Prometheus JMX Exporter runs as an agent in the corresponding pods (e.g. Kafka or ZooKeeper pods). It does not have its own pod. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Please use this to only for bug reports. For questions or when you need help, you can use the GitHub Discussions, our #strimzi Slack channel or out user mailing list.
Describe the bug
Prometheus Exporter pod is not being created
To Reproduce
Steps to reproduce the behavior:
kubectl apply -f file.yaml
Environment (please complete the following information):
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.9-gke.3200", GitCommit:"92ea556d4e7418d0e7b5db1ee576a73f8fc47e91", GitTreeState:"clean", BuildDate:"2023-01-20T09:29:29Z", GoVersion:"go1.18.9b7", Compiler:"gc", Platform:"linux/amd64"}
Metrics Being exposed
YAML files and logs
Attach or copy paste the custom resources you used to deploy the Kafka cluster and the relevant YAMLs created by the Cluster Operator.
Attach or copy and paste also the relevant logs.
To easily collect all YAMLs and logs, you can use our report script which will automatically collect all files and prepare a ZIP archive which can be easily attached to this issue.
The usage of this script is:
./report.sh --namespace <string> --cluster <string> [--bridge <string>] [--connect <string>] [--mm2 <string>]
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions