# OpenSearch Alert-as-Code

**URL:** https://forum.opensearch.org/t/opensearch-alert-as-code/16070
**Category:** Alerting
**Tags:** discuss
**Created:** [September 27, 2023, 10:32am UTC](https://forum.opensearch.org/t/opensearch-alert-as-code/16070 "2023-09-27T10:32:10Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Coexist](https://avatars.discourse-cdn.com/v4/letter/c/a698b9/32.png) [@Coexist](https://forum.opensearch.org/u/Coexist)
#### Post date: [September 27, 2023, 10:32am UTC](https://forum.opensearch.org/t/opensearch-alert-as-code/16070/1 "2023-09-27T10:32:10Z")

</div>

**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser):  
2.7

**Describe the issue** :  
Hi team,

Is it possible to create a CI/CD for OpenSearch Monitors? Say from an array of JSON of the “Monitors”? How can we get the Monitor ID remotely???

GET and Update Monitor API seem limited to one entity as of this writing.

Thanks!

**Configuration** :

**Relevant Logs or Screenshots** :

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/3/33547ea01a5b12dcca2958411d3edd97ae2ea8c1.png) [@system](https://forum.opensearch.org/u/system)
#### Post date: [November 26, 2023, 10:32am UTC](https://forum.opensearch.org/t/opensearch-alert-as-code/16070/2 "2023-11-26T10:32:18Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
