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.

Sign up for GitHub

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

Jump to bottom

Notification Debuggability #17718

Closed
4 tasks done
mohityadav766 opened this issue Sep 5, 2024 · 1 comment · Fixed by #18199
Closed
4 tasks done

Notification Debuggability #17718

mohityadav766 opened this issue Sep 5, 2024 · 1 comment · Fixed by #18199
Assignees
@Siddhanttimeline
Labels
Alert & Notifications

Comments

@mohityadav766
Copy link
Contributor

mohityadav766 commented Sep 5, 2024 •
edited by Siddhanttimeline
Loading

Currently, we have difficulty tracking the state of a changeEvent in case of failure.
We need the following information to be built so it RCA for failed message become easy.

  • Tracking the current state of publisher , the available event in the queue(change_event table) and the current offset run for the publisher.
  • Each publisher can have n destination and it is crucial to differentiate the event failed for which destination , we have consumer_dlq that can be utilized , but as of today that is working at the consumer level and not at the destination level.
  • Adding Test Message for all Slack, MsTeams , Email , to allow users to test working functionality while create the alerts.
  • Provide api for errored event , with the failureContext and also for which destination that particular event failed
@Siddhanttimeline
Copy link
Contributor

Adding Test Message for all Slack, MsTeams , Email , to allow users to test working functionality while create the alerts.

Test Alert Destination PR
Improvement iterations will follow.

@Siddhanttimeline Siddhanttimeline mentioned this issue Sep 11, 2024
Open
8 tasks
@Siddhanttimeline Siddhanttimeline mentioned this issue Oct 10, 2024
Merged
9 tasks
harshach added a commit that referenced this issue Oct 30, 2024
@Siddhanttimeline @harshach
Fixes #17718 : Notification Debuggability (#18199)
f0fc482 
* create EventSubscriptionDiagnosticInfo

* API for failedEvents

* migrations

* add index on source

* list all failedEvents optionally filtered by source

* refactor

* refactor

* getSuccessfullySentChangeEventsForAlert API

* increase defaultValue of limit to 100

* resolve conflicts

* listEvents API with 'failed', 'successful,' and 'unprocessed' query parameters

* fix description

* eventSource as enums

* refactor name.

---------

Co-authored-by: Sriharsha Chintalapani <harshach@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Siddhanttimeline Siddhanttimeline

Labels
Alert & Notifications
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes #17718 : Notification Debuggability open-metadata/OpenMetadata
2 participants
@Siddhanttimeline @mohityadav766