[swiderski.maciej]

alright, here it is. An initial version of the alert definition templates migration utility. Seems to be working fine at least for the cases I have. So all the comments and feedback more than welcome.

Two things that are missing in REST api that are bit unfortunate:

• no way to get and then set alert description which is not a critical thing but makes the alert definitions more readable
• no way to get and then set "disable web fire" property which is rather essential.

So would be good to have that included in next versions of REST api so it will get complete.

Maciej

[swiderski.maciej]

Any feedback if that was anywhere close the right way of doing it?

[lzoubek]

Hi,

thanks for sharing the code. I found the only potential issue with your way you transform alert notifications. There is a field "extraConfig" you may want to import/export as well, but AFAIK this field makes sense only if you notification is supposed to run a resource operation.

What do you mean by "disable web fire"? In case you refer to dampening, you should be able to do it similar to this

[swiderski.maciej]

sorry it was a typo - it should be "disable when fired" to avoid duplicated notifications for some of the alerts.

Thanks for feedback about extraConfig, will look into it and include if possible.

Maciej

[lkrejci]

alertParameters and extraParameters are the devil in the detail ;-) This is where the pluggable notifications store their various config options... And the format and type of data varies wildly - user ids, resource ids, role ids, package ids, you name it and it's all installation dependent - there is no easy way of transferring these without a mapping  of sorts (which AFAIR you already use in your code). And this is where with stumbled in the past - we were scared by the amount of work needed to come up with a user-friendly and capable mapping creation tool.