SMS alerts rely by default on gateways with an email to SMS support. This means that the gateway should be able to send an SMS when an email is sent to <phone-number>@smsgatewayprovider.com.
In case there isn't a supported carrier in your country, you can instead use the HTTP Request templates with the gateways that support API calls. Here is a small example using the Nexmo SMS gateway.
-
Go to nexmo.com and sign up for a new account.
-
Go to the AppDynamics Controller and navigate to Alert & Respond.
-
Choose HTTP Request Templates in the left menu.
-
Click New to add new template.
-
Add a custom variable for the recipient number. You can choose a default value.
- Configure request URL to use POST and the endpoint https://rest.nexmo.com/sms/json
-
Set payload MIME type to application/json and the payload to
{ "api_key":"<INSERT_NEXMO_API_KEY>", "api_secret":"<INSERT_NEXMO_API_SECRET>", "to":"${mobile}", "from":"AppDynamics", "text":"${latestEvent.displayName}: ${latestEvent.eventMessage}" } - Click Save.
- You can then click Test and Add event type to send a test SMS and see that Nexmo is not reporting any errors.
- Create new action by navigating to Alerts & Respond > Actions > New and choose Make an HTTP request.
- Create new policy by navigating to Alerts & Respond > Policy > Create Policy and choose the events that you like to trigger an action on.
- Click Actions and choose the newly created request Action.
We've done the same thing with the STIX service here in Norway. See example:
You can have more recipients, just add numers like this: ["number1","number2","number3"]
