How to propagate correctly tags into Opsgenie

[rschirin]

Hey there,
I'm trying to integrate Elastalert2 with Opsgenie. Everything is fine but the propagation of tags from heartbeat rule to Opsgenie alert.
Basically, the first alert is created with correct tags using the configuration below:

opsgenie_tags:
   - "{tags[0]}"
   - "{tags[1]}"
   - "{monitor[id]}"

while next one maintains the same values even if they are different.
How should I fix that?

[jertel]

Looks like a bug on this line:

elastalert2/elastalert/alerters/opsgenie.py

Line 91 in 93ee6ff

self.tags[i] = tag.format(**matches[0])

It's formatting the tags on the first alert and saving the newly formatted tags over the top of the original configured tags, instead of saving the formatted tag into a temporary variable. Here's the offending commit: 386708e

It should be a simple fix if you're up for a PR. If you're unable then someone may eventually get to it.

[nsano-rururu]

Is the following pull request on yelp / elastalert a relevant fix?

Fix Incorrect Opsgenie Tags Formatting
Yelp/elastalert#2884
Patch opsgenie tags overwritten after first alert
Yelp/elastalert#2840

[rschirin]

So, is it possible to use those pull requests or should be created a new one?

[jertel]

Fixed in #537.