Here are the classes, structs, unions and interfaces with brief descriptions:
Alerts | Provides a function to get recent messages from a monitoring job |
EC2Client | Ability to provision, start, stop, describe, and reboot EC2 instances |
Email | Provides an API to send plain text or html email |
FeedClient | Provides an API to get recent data from a data feed |
File | Provides an API to read data files. Datafiles are uploaded through the application or using the REST API |
HttpClient | Provides an API to perform HTTP POST and GET operations |
HttpResponse | Contains the data resulting from an HTTP request |
IncidentClient | |
Leftronic | A Rest client that posts data to a Leftronic dashboard |
Monitor | Provides access to the harchive and monitoring backend |
Neustar | This is the main object in the alert policy script. It is put into the Javascript environment as the variable neustar. It contains these other objects: |
PagerDuty | Provides a client to PagerDuty. It provides calls to trigger, resolve and get the status of open incidents |
RumClient | Provides the ability to retrieve recent data from WPM RUM |
S3Client | Provides the ability to get,put,list,copy and delete objects in S3 |
Scheduler | Provides the ability to immediately reschedule monitoring jobs |
SMSClient | Provides the abilty to send SMS messages |
Store | Provides a key value store to persist data between different executions of alert scripts. The store is accessible only to the alert policy that is running |
Template | Provides the ability to render templates. The templates available are the mustache templates used to generate the alert emails. You can use your own mustache template |
Util | |