How to share task id between altert manager receivers

[tao fu]

Hi 

I'm trying to share task id between Jira receiver and email receiver. But I can't find any reference.  Seems I can't share the task id between Jira receiver and email receiver.

This is the Scenario:  when a alert fired, I want to creat  a Jira task to tracing the issue, then send the task id to the operator.  

Is it possible to implement the process by using alert manager? Is possible, could you please  share some idea? 

Thanks in advance~!

Best regards

[Matt Doughty]

I don't think you can do that sharing. Can't you have jira notify oncall on ticket creation? 

--Matt

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/5356a62d-81e5-41e6-9aaa-43062633cb02n%40googlegroups.com.

[tao fu]

Hi Matt

Thank you for your reply. Yes I can have jira notify oncall on ticket, but from architecture perspective , this kind of work should belong to the centralized alert or event centor. So it's better implement in alert or event centor(Alert manager). Jira is only one Scenario.

[tao fu]

Hi Matt

Or if I want to extent alert manager for sharing data between receivers, where should I begin with?

[Stuart Clark]

On 17/03/2021 13:30, tao fu wrote:

Hi Matt

Or if I want to extent alert manager for sharing data between receivers, where should I begin with?

在2021年3月17日星期三 UTC+8 下午9:17:31<tao fu> 写道：

Hi Matt

Thank you for your reply. Yes I can have jira notify oncall on ticket, but from architecture perspective , this kind of work should belong to the centralized alert or event centor. So it's better implement in alert or event centor(Alert manager). Jira is only one Scenario.

This sounds a bit out of scope for Alertmanager. Rather than being an "alert centre" it is really and "alert director" which simply takes in alerts, de-duplicates/groups/inhibits and then sends to receivers based on some filtering rules. The general advice for more complex use cases is to use a tool designed for such things (for example PagerDuty or OpsGenie) - commonly things like escalations, business rules, etc.

-- 
Stuart Clark

[tao fu]

Hi  Stuart Clark

Thank you for your idea. It make sence.  I realize that alert manager should be the alert center.  That means the purpose of alert manager is sending the alert as much as sample and stable. So the process should be in other component. Because complex flow will bing new trouble.