Is there a way to change what is forwarded under resHierarchy? Or better, is there a way to tell it to return specific metrics or properties?

I'm also seeing that that "${symptoms}" returns blank if I use it in a custom payload.

> Is there a way to change what is forwarded under resHierarchy?
A: Sorry, resHierarchy is now disabled. You can use tags instead. If you have custom tags on objects, you can specify this tag name and all tags associated to the object of the alert will be included. Please see v1.4 release notes for details.

> Or better, is there a way to tell it to return specific metrics or properties?
A: Unfortunately the number of metrics is limited to ones specified in Imset documentation. If you would like to include additional metrics, please open a bug here, I'll do my best to add those.

> I'm also seeing that that "${symptoms}" returns blank if I use it in a custom payload.
A: symptoms field provides the symptoms that are specified in alert definition and are active on triggered object. In case the alert definition is based on other objects (e.g. children, parents, etc.) the triggered symptom may not be detected on alert's object. In these cases the symptoms will appear empty.

Thank you! Is it possible to change the headers for the forwarded message?

no

@Gor Ghazaryan, Is it possible to use this with a multi mode vROps setup, so in case a node fails , another node takes over?

vROps can send the alerts from different nodes, however Imset knows only about one of them, so communication from Imset to vROps always goes through this known hostname. This is done due to some security considerations.
This said it's best if you set the master node's address in your config, or, if you have HA enabled, the HA master hostname.

Sorry, I was not clear enough. I have it configured where it is successfully sending the custom payload after communicating with the master node specified in the config file.

What I am hoping to do is have imset communicate automatically with a secondary node if the primary one fails. With the current setup, I believe we need to manually configure the new node in the config.

Yes, unfortunately you need to configure it again.

@Gor Ghazaryan, How can I set the color to green if the alert was cancelled? Sorry that I'm a JSON "noob".

Sorry for late response. You need to set the "color" option in slack's payload, under "attachments". You can find more information about this in Slack API documentation: https://api.slack.com/messaging/composing/layouts#attachments

@Gor Ghazaryan Any plans to release a throttle feature for REST Notifications Helper? It would be very useful to limit the number of notifications per time period to a user-defined max threshold in order to prevent messaging storms. It would be especially useful if this threshold could be set per alertName and a message would go out saying "Throttling messages for alertName due to threshold X exceeded" for example.

Thanks for the suggestion, Shane. With current design it will be hard to achieve this as the service doesn't keep any information about the alerts.
I understand that the feature you're suggesting will be very good to have and I'll try to think of a way to implement it