Add support for tags on destinations / monitors about alerting HOT 3 CLOSED

Hi @phillbaker,

We are definitely missing a GET Destination API which would help, but to further clarify on your issue are you looking for a way to tag and group destinations or a way to simplify the API creation workflow when adding a destination?

I know when using the API to configure alerting we do require the destination ID in the action configuration which can be annoying to get. It seems like it might be easiest to allow the user to either uniquely tag the destination or even provide the destination document_id used so that they can directly refer to that inside the alerting config.

from alerting.

Thanks for taking a look @dbbaughe, I conflated a few issues, happy to add more examples if it'd help.

to further clarify on your issue are you looking for a way to tag and group destinations or a way to simplify the API creation workflow when adding a destination?

A way to tag and group destinations!

it might be easiest to allow the user to either uniquely tag the destination

Agreed - tags and a search endpoint (similar to monitors) would be a big step in this direction.

from alerting.

Closing in favor of opensearch-project/alerting#40

from alerting.