# Unable to change the INTERVAL part of the monitor using update monitor API

**URL:** <https://discuss.elastic.co/t/unable-to-change-the-interval-part-of-the-monitor-using-update-monitor-api/296665>\
**Category:** Kibana\
**Created:** [February 8, 2022, 9:58pm UTC](https://discuss.elastic.co/t/unable-to-change-the-interval-part-of-the-monitor-using-update-monitor-api/296665 "2022-02-08T21:58:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![N\_Pusapati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/n_pusapati/32/101562_2.png) [@N\_Pusapati](https://discuss.elastic.co/u/N_Pusapati)\
**Post date:** [February 8, 2022, 9:58pm UTC](https://discuss.elastic.co/t/unable-to-change-the-interval-part-of-the-monitor-using-update-monitor-api/296665/1 "2022-02-08T21:58:26Z")

</div>

Hi I am pretty new to Elasticsearch, trying to setup monitors on certain indexes based on the Extraction Query response. I am trying to achieve this using Create/Update monitor APIs. Everything works as expected except one where the INTERVAL is still showing as 1 MINUTES where as I passed different CRON expression or INTERVALS. Defaults to INTERVAL 1 MINUTES is causing too many alerts. Can any one please help me on how to address this default INTERVAL issue?

Would appreciate your help!  
Example:

```auto
{
  "type": "monitor",
  "name": "MONITOR_NAME",
  "enabled": true,
  **"schedule": {**
 **"period": {**
 **"interval": 720,**
 **"unit": "MINUTES"**
 **}**
 **},**

```

---

<div class="post-metadata">

**Author:** ![N\_Pusapati](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/n_pusapati/32/101562_2.png) [@N\_Pusapati](https://discuss.elastic.co/u/N_Pusapati)\
**Post date:** [February 8, 2022, 10:05pm UTC](https://discuss.elastic.co/t/unable-to-change-the-interval-part-of-the-monitor-using-update-monitor-api/296665/2 "2022-02-08T22:05:42Z")

</div>

![Screen Shot 2022-02-08 at 4.04.03 PM](https://us1.discourse-cdn.com/elastic/original/3X/b/8/b882acb4ea9357aaa6aa7d8bd574a0466abaa576.png)  
 ![Screen Shot 2022-02-08 at 4.04.12 PM](https://us1.discourse-cdn.com/elastic/original/3X/3/2/32898514908bce2cdd419839f30d534fab7d3491.png)

Attached the screen shots representing the issue

---

<div class="post-metadata">

**Author:** ![gmmorris](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gmmorris/32/72624_2.png) [@gmmorris](https://discuss.elastic.co/u/gmmorris)\
**Post date:** [February 8, 2022, 11:13pm UTC](https://discuss.elastic.co/t/unable-to-change-the-interval-part-of-the-monitor-using-update-monitor-api/296665/3 "2022-02-08T23:13:23Z")

</div>

Hi @N_Pusapati  
Welcome to the Elastic community 🙂

Looking at your configuration above I believe you're not in fact using Elastic's Alerting framework, but rather Amazon's OpenSearch.  
This is not the Elastic distribution of Kibana, but rather an Amazon specific product ([see the differences here](https://www.elastic.co/aws-elasticsearch-service)). We, unfortunately, cannot offer support for Amazon's distribution, so you may have better luck asking in their forums.

It's also worth noting that we do have an alerting feature as part of our distribution as well, which we are happy to offer support for: [https://www.elastic.co/what-is/kibana-alerting](https://www.elastic.co/what-is/kibana-alerting)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 8, 2022, 11:13pm UTC](https://discuss.elastic.co/t/unable-to-change-the-interval-part-of-the-monitor-using-update-monitor-api/296665/5 "2022-03-08T23:13:23Z")

</div>

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