Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start collecting telemetry for subscription handling #602

Open
1 task
SandGrainOne opened this issue Oct 15, 2024 · 0 comments
Open
1 task

Start collecting telemetry for subscription handling #602

SandGrainOne opened this issue Oct 15, 2024 · 0 comments
Labels
kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@SandGrainOne
Copy link
Member

SandGrainOne commented Oct 15, 2024

Description

Introduce telemetry for key elements ragarding the subscription handling. We want to know how much time it takes to process subscriptions for an event and whether subscriptions are valid. Meaning if the consumer is still allowed to subscribe to the event it was created for.

This issue assumes that we already have OpenTelemetry turned on and that there are other telemetry already being registered. If this is not the case the issue would require more tasks for setting up the framework for using OpenTelemetry.

Additional Information

This issue where created during issue cleaning where #15 came up. We want to collect more data about the possible issue before taking any actions.

Tasks

  • Consider what type of metrics to use for each of the metrics below. e.g counter or rate
  • Create a metric for how long it takes to process an event for subscribers
  • Create a metric for the amount of failed authorizations when checking subscriptions
  • Create a dashboard to visualize the matrics

Acceptance Criterias

  • We can see the two new metrics on a dashboard in /monitor/.

Dependencies

@SandGrainOne SandGrainOne added kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue. labels Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users. status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Development

No branches or pull requests

1 participant