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

Community

Other: Multiple SLA policy in HVR 6

HVR Admins User

Hi Team,

We recently migrated one of our HVR5 production hub to HVR6 hub. We found an issue with Alerting mechanism which looks different from HVR5 hub. 

In HVR5 we were able to define multiple alert policies each having different SLAs and each may be going to different Slack channels or Mail Ids as per the different SLAs for latency. 

But in HVR6 there is no option to link a specific SLA action to specific alerts. One SLA is linked to every alert we create.

So if I want an alert going to 'dba' slack channel if latency goes beyond 20 mins and alert going to 'support' slack channel if latency goes beyond 60 mins and alert going to 'dba-on-call' mail ID if latency goes beyond 120 mins.

I am advised to raise feature request for this as it does not already exist in HVR 6 (But it exist on HVR 5 and we were able configure the scenarios I mentioned, in HVR 5).

It would we great if this can be rolled out as soon as possible as it affects our alerting and paging policies.

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Mark Van de Wiel User

    Hi There,

    I acknowledge that the alert system in HVR 6 provides gaps relative to HVR 5. I am planning a project in the next few quarters to address this. Your need to define multiple SLAs will be included in this project.

    FYI ticket reference for the project is T-585631 in case you want to follow up specifically on the improvements to alerts.

    Thank you,
    Mark.