michaeljmarshall commented on PR #299:
URL:
https://github.com/apache/pulsar-helm-chart/pull/299#issuecomment-1281603979
One relevant item to verify is metric label parity. Labels are often
added/modified by the relabel config in the scrape definition.
Metric from publicly available pulsar-helm chart:
>
pulsar_broker_lookup{app="pulsar",cluster="p-pulsar",component="broker",controller_revision_hash="p-pulsar-broker-5fc786b7c8",
exported_cluster="p-pulsar",instance="172.17.0.9:8080",job="broker",kubernetes_namespace="default",kubernetes_pod_name="p-pulsar-broker-0",quantile="0.5",release="p",statefulset_kubernetes_io_pod_name="p-pulsar-broker-0"}
Metrics from the helm chart deployed with this PR at this point in git
history.
> pulsar_broker_lookup{app="pulsar", cluster="test-pulsar",
component="broker", container="test-pulsar-broker",
controller_revision_hash="test-pulsar-broker-5d4489dc7d", endpoint="http",
exported_cluster="test-pulsar", instance="172.17.0.9:8080", job="broker",
kubernetes_namespace="default", kubernetes_pod_name="test-pulsar-broker-0",
namespace="default", pod="test-pulsar-broker-0", quantile="0.5",
release="test", statefulset_kubernetes_io_pod_name="test-pulsar-broker-0"}
The scrape definitions are pretty different, but ultimately, the broker's
current scrape definition is created by the already established
`broker-podmonitor.yaml`, so this might be a non-issue.
--
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]
