Skip to content
This repository was archived by the owner on Dec 11, 2023. It is now read-only.
This repository was archived by the owner on Dec 11, 2023. It is now read-only.

Additional Metadata Needed on Prometheus and Grafana #157

Description

@thebigstevo

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions