Hi Cloudar,

If you already have the monitors list based on tag for which you want to change actions, you can do it from our web client at Admin>Inventory>Bulk Action.

• Select the monitors you want to apply/change action, and click on Bulk Action.
• From the popup that opens, click on Modify Actions.
• In the the form, select the monitors if it's not selected already, select the action from drop down and click on Add button.
• Click on Save to submit your changes

You can also do this from bulk_action API.
Endpoint: /api/monitors/bulk_action
Request Method Type: PUT
Request Payload:

1. {
     "monitors": [
       "123456789012345678",    //ID of monitor 1
       "123456789012345679",    //ID of monitor 2
       "123456789012345680"    //ID of monitor 3
     ],
     "bulk_action_type": 5,    //constant for altering actions
     "action_ids": [
       {
         "action_id": "123456789012345681",     //ID of action you want to apply
         "alert_type": 0    //execute on down
       }
     ]
   }
   

Possible value for alert type:
0 : Execute on Down
1 : Execute on Up
2 : Execute on Trouble
20: Execute on any attribute status change
-1: Execute on any status change

Aniket Sinha
Site24x7 Team

Hi Aniket,

Hello Tom,

You were looking at the right spot, but unfortunately this API is currently not documented.
We will document this API in the next update we do.

On a side note, were you trying to edit each monitor individually to set actions on them?

Yes Tom, you need to pull the whole monitor list JSON and parse it to filter the monitors you need.

However, if you have tagged your EC2 Instances using Name tag, then we will pick that tag's value as display name in Site24x7, other wise default display name is the instance id. An ugly method of getting monitor id's is to use name based GET API. This is another undocumented API where you can get monitor details based on their display name. Here, you would make multiple API calls to get monitor id's. So, I wouldn't recommend using it.

This is the API end point in case you want take a look at it:

1. https://site24x7.com/api/monitors/name/<displayName>

Answering your 2nd question, it's currently not possible to add a default action on EC2 monitors. Reason behind this is the parent AMAZON monitor itself doesn't support configuring Actions. We would take this as a feature request.

However, we have Configuration Template for Server monitors, but even that doesn't support actions currently. You can find it in web client  and read about it in help docs.

It's a pity that one cannot add Actions as a default, as they are the only way to properly integrate with services like OpsGenie. And in autoscaling environments, newly spawned instances won't have any Actions (and thus alerting) attached.

Hi Aniket,

Hi Tom,
Sorry for the time it took to analyze this.

The latest agent(v 16.1.0) installed on the instance sends the instance id only during initial setup. That's how you are getting the details of some servers.

There was an temporary issue at our end, due to which we missed to capture this information sent by the agents during initial setup.

To prevent this from happening, our next agent release will send the instance id again if it's not present in our systems already. This new agent version is already being tested and should be rolled out in a couple of weeks. Once released, please upgrade your server agents with the updated version, so that instance id will be captured for the missed servers.

Hi Aniket,

Hi Aniket,

Hi Tom,

This does not look good. Are you getting instance ids for Linux instances?
Windows server agent is yet to support this, and I'm afraid there is no manual way to update/patch this until we release the new agent for windows servers.

Hi Aniket,