# Monitor & destination meta data

**URL:** <https://forum.opensearch.org/t/monitor-destination-meta-data/684>\
**Category:** Alerting\
**Created:** [May 14, 2019, 10:45pm UTC](https://forum.opensearch.org/t/monitor-destination-meta-data/684 "2019-05-14T22:45:38Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![shah](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/shah/32/150_2.png) [@shah](https://forum.opensearch.org/u/shah)\
**Post date:** [May 14, 2019, 10:45pm UTC](https://forum.opensearch.org/t/monitor-destination-meta-data/684/1 "2019-05-14T22:45:38Z")

</div>

Is it possible to add meta-data to a `monitor` or `destination` definition, for example like `ingest pipelines` has a `description` attribute.

My use case is to organize alerts under high level categories, for example `Cluster Health`, `Document Metrics` and pass that along from the `trigger ctx variables` to the `action template`.

---

<div class="post-metadata">

**Author:** ![lucaswin-amzn](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/lucaswin-amzn/32/192_2.png) [@lucaswin-amzn](https://forum.opensearch.org/u/lucaswin-amzn)\
**Post date:** [May 15, 2019, 4:04pm UTC](https://forum.opensearch.org/t/monitor-destination-meta-data/684/2 "2019-05-15T16:04:31Z")

</div>

Hi @shah,  
The first requirement I see here is that the description would need to be in JSON format in order to be used in the `ctx` variables.

Just to clarify you would like to just have some text attached to monitors and destinations?

---

<div class="post-metadata">

**Author:** ![shah](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/shah/32/150_2.png) [@shah](https://forum.opensearch.org/u/shah)\
**Post date:** [May 16, 2019, 6:17am UTC](https://forum.opensearch.org/t/monitor-destination-meta-data/684/3 "2019-05-16T06:17:51Z")

</div>

Hi @lucaswin-amzn,

Yes that is correct, the aim here is to organize and track alerts going to a custom webhook and be able to know what category the alert falls under based on some `monitor meta data`.

---

<div class="post-metadata">

**Author:** ![lucaswin-amzn](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/lucaswin-amzn/32/192_2.png) [@lucaswin-amzn](https://forum.opensearch.org/u/lucaswin-amzn)\
**Post date:** [May 20, 2019, 4:53pm UTC](https://forum.opensearch.org/t/monitor-destination-meta-data/684/4 "2019-05-20T16:53:43Z")

</div>

Hi @shah,

I don’t see a justification to add this kind of meta-data purely for categorization. You could put this information into the monitor / trigger name and then access it using the `ctx` variable while sending an alert, or am I understanding your use case incorrectly?

Thanks,  
Lucas Winkelmann

---

<div class="post-metadata">

**Author:** ![shah](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/shah/32/150_2.png) [@shah](https://forum.opensearch.org/u/shah)\
**Post date:** [May 21, 2019, 4:22am UTC](https://forum.opensearch.org/t/monitor-destination-meta-data/684/5 "2019-05-21T04:22:11Z")

</div>

Hi @lucaswin-amzn,

Our current work around is to use the the `name attribute` to scope the category / namespace.

Thanks for the insights!

---

<div class="post-metadata">

**Author:** ![skkosuri-amzn](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/skkosuri-amzn/32/935_2.png) [@skkosuri-amzn](https://forum.opensearch.org/u/skkosuri-amzn)\
**Post date:** [August 31, 2020, 10:49pm UTC](https://forum.opensearch.org/t/monitor-destination-meta-data/684/6 "2020-08-31T22:49:02Z")

</div>

Closed on August 31, 2020, 10:49pm UTC