Other: HVR Alert section: improvement in Custom alert header
Planned
In HVR, in Alert we have an option as Custom alert header
But this Custom alert header preffix with default header which is irrelevant in case of custom header
if there a custom header then we should not add default header. This breaks the purpose.
example alert we receive:
HVR RRE rre_tps_fct3 Health check status in hvr_hub_qa05 sf_rre_hvr_monitoring_lantecy: latency exceeded (worst 3m 57s>2m 0s) by 7 jobs in 4 channels in hvr_hub_qa05 on someHostName
Custom header as HVR RRE {channel} Health check status in {hub}
now we are sending duplicate info in header. Custom + default
-
Hi Tushar,
I agree it doesn't seem to make much sense to still default a part of the custom alert header. We will try to fix this in the upcoming releases.
Best regards,
Edwin
Please sign in to leave a comment.
Comments
1 comment