Open
Conversation
Add a source heartbeat no-incremental-event alarm that starts after heartbeat-enabled sources have no captured incremental event for 60 seconds. Record incremental monitor and capture timestamps from observable samples, initialize task alarm settings and templates, and recover the alarm when downstream pending events indicate capture is no longer idle. Harden the alarm path against missing user details, DAG nodes, invalid timestamps, and recovered alarm ordering. Refs: TAP-11387
…evelop # Conflicts: # manager/tm/src/main/resources/init/idaas/version
🤖 Augment PR SummarySummary: Adds monitoring and alarming for “source heartbeat enabled but no incremental events captured”. Changes:
Technical Notes: The new alarm uses a 1-minute threshold and attempts to suppress alerts when downstream is blocked (pending captured events not yet enqueued). 🤖 Was this summary useful? React with 👍 or 👎 |
Guard the stream enqueued metrics consumer before counting Tapdata events. The enqueued path now matches read-complete handling by skipping countTapdataEvent when the event list is null or empty, avoiding dropped metrics and warning logs from null upstream input. Refs: TAP-11387
Report the actual source heartbeat idle duration in TASK_SOURCE_NO_INCREMENTAL_EVENT notifications instead of the static 60 second threshold. Pass the alarm evaluation time into the start-alarm payload and calculate idleSeconds from now minus the selected baseline. Restore the source idle alarm path so it still runs when node alarm rules are absent. Refs: TAP-11387
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.