I am currently exploring the monitoring capabilities of Prometheus/Grafana. While analyzing the timestamp-based events that pass from the source to the broker and then to the target, I have noticed information such as the following:
{__name__="broker_trigger_event_count", broker_name="redis-broker", container="broker", delivered="true", endpoint="metrics", instance="<ip-addresss>:9090", job="monitoring/triggermesh-components", namespace="default", pod="redis-broker-rb-broker-bc55df4b-sm56x", sent_type="com.google.cloud.storage.notification", trigger_name="lambda-trigger"}
To effectively identify the event flow, it would be beneficial to have additional event metadata, such as the event name and other relevant details. This would greatly enhance the identification process and provide better insights into the events being monitored.
I am currently exploring the monitoring capabilities of Prometheus/Grafana. While analyzing the timestamp-based events that pass from the source to the broker and then to the target, I have noticed information such as the following:
{__name__="broker_trigger_event_count", broker_name="redis-broker", container="broker", delivered="true", endpoint="metrics", instance="<ip-addresss>:9090", job="monitoring/triggermesh-components", namespace="default", pod="redis-broker-rb-broker-bc55df4b-sm56x", sent_type="com.google.cloud.storage.notification", trigger_name="lambda-trigger"}To effectively identify the event flow, it would be beneficial to have additional event metadata, such as the event name and other relevant details. This would greatly enhance the identification process and provide better insights into the events being monitored.