Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Other: HVR6 latency email alert feature enhancement

Kervin Pagaran User

We want to keep the hub-level action and to have an additional/separate configuration latency alerts for certain locations and/or channels are to be able to meet the following requirements:

1. To configure hub-level latency alert for all the active channels in the hub for internal monitoring and support. This is to automatically receive latency alerts internally within the team whenever there are new additional/upcoming channels to be added in the hub, this also helps the team to save effort doing routine administrative tasks registering those additional channels in the alerts.

2. To configure separate latency alerts with certain locations/channels in scope for different projects with different recipients and team to receive particular alerts.

3. To configure separate latency alerts with certain locations/channels in scope for different application users with different recipients and team who are requesting to receive particular alerts for their monitoring.

In further details, we have one-to-many replication setup. Each source system that we replicate from SAP is composed of one (1) shared capture job and five (5) integration jobs going to different target locations/servers. In other words, we're doing N-furcation setup. Each target location has dedicated application users using it in a particular project. Both of them would be requesting separate latency alerts for certain locations/channels that are within their scope with different latency threshold/requirement. The latency thresholds are as follows depending on which application users are requesting an alert.

10min

15min

30min

1hr

For more details and background of the problem, please refer to the following case.

Id #131257

HVR6 latency email alert is not working for certain Channels/Locations

Please sign in to leave a comment.

Comments

4 comments

Date Votes
  • Mark Van de Wiel User

    Alerts can be configured using the Scheduling action (attribute LatencySLA). I believe this addresses the majority of the items requested here including the ability to get alerts per channel per target.

    Reference to the documentation: https://fivetran.com/docs/local-data-processing/action-reference/scheduling#parameters

    Mark.

  • Kervin Pagaran User

    Hi Mark / Fivetran support,

     

    Seems that this feature enhancement request was being addressed in LDP/HVR version 6.1.0/36, could you please confirm?

     

    Thanks,

    Kervin

  • Mark Van de Wiel User

    Kevin,

    There was an issue with the latency SLA messages that was addressed in 6.1.0/26. That release also introduced a fix to filtering regarding SLAs, but that was still broken after that (or broke again) which was subsequently fixed in 6.1.0/35. So 6.1.0/36 you referenced has all the fixes for latency SLAs that we have delivered.

    Hope this helps.
    Mark.

  • Kervin Pagaran User

    Hi Mark,

     

    Great news! I can confirm that we are now able to configure and receive latency email alerts for certain channels/locations on top of the hub level alerts.

     

    Thank you for the confirmation and support.