Trigger Actions
About
Trigger actions are a mechanism that performs specific tasks when DNS record health checks fail. When the health check(s) defined for health scenarios fail, the trigger action is activated and executes the specified operation.
How to Add?
To add a new Trigger Action, navigate through the TR7 ASP web interface: Global Traffic Manager (GTM) > Settings > Trigger Action > Add.
Interface
Trigger Actions Listing Screen
The list of all Trigger Actions added to the TR7 ASP device can be accessed by navigating through "Global Traffic Manager (GTM) > Settings > Trigger Action". On this screen, Trigger Actions can be added, edited, and deleted.
- 1 (Information to be Displayed in the Table)
The table displaying the list of Trigger Actions allows selecting which information will be shown or hidden.
The selectable information, which is selected by default, includes:
- Name
- Trigger Type
- 2 (Add)
Clicking the Add button opens the form for creating a new Trigger Action Profile.
- 3 (Edit)
Clicking the Edit button opens the editing screen for the relevant Trigger Action Profile.
- 4 (Delete)
Select one or more Trigger Actions and click the Delete button to remove them from the TR7 ASP device..
- 5 (Search)
Used to search all expressions in the table.
- 6 (RegExp Search)
Used to search all expressions in the table using regular expressions.
- 7 (Column Based Search)
Used to search all expressions column-based.
- 8 (Page Information)
Displays the total number of Trigger Actions and how many are listed on the current page.
- 9 (Page Size)
Allows selecting the maximum number of Trigger Actions displayed per page. Arrows can be used to navigate between pages.
- Preview of the Selected Trigger Action
After following the steps "Global Traffic Manager (GTM) > Settings > Trigger Actions", clicking on any Trigger Action opens a window on the right side of the screen containing the information related to that action.
The preview can be closed by clicking the (x) button located at the top right of the opened window.
Interface
Trigger Action Addition Form
A new Trigger Action is added to the TR7 ASP device by following the steps "Global Traffic Manager (GTM) > Settings > Trigger Action > Add".
- Name
The name of the Trigger Action to be created is entered.
- Trigger Type
- vDevice
On which vDevice the vService to be created will be opened is selected.
- Route Table
The Route Table through which the added Trigger Action will be applied is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, click here.
- User
The username for connecting to the Oracle server is entered.
- Password
The password for the user connecting to the Oracle server is entered.
- Connection String
The IP:Port/Path information for connecting to the Oracle server is entered.
- Oracle Action
It is used to perform Oracle trigger actions based on scenarios. In the scenarios, it is possible to connect to the Oracle server and execute commands. The results of the executed commands can then be checked for the expected text and lines.
- vDevice
On which vDevice the vService to be created will be opened is selected.
- Route Table
The Route Table through which the added Trigger Action will be applied is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, click here.
- Address
The IP:Port information is entered for the Trigger Action to be created.
- Path + Query
The Path + Query information for the request to the Service is entered. If left empty, the requests will be made to / (root).
- Method
The HTTP method to be used for the Trigger Action is selected.
- List of HTTP Methods Supported by TR7
| Method |
|---|
| ACL |
| BASELINE-CONTROL |
| BIND |
| CHECKIN |
| CHECKOUT |
| CONNECT |
| COPY |
| DELETE |
| GET |
| HEAD |
| LABEL |
| LINK |
| LOCK |
| MERGE |
| MKACTIVITY |
| MKCALENDER |
| MKCOL |
| MKREDIRECTREF |
| MKWORKSPACE |
| MOVE |
| OPTIONS |
| ORDERPATCH |
| PATCH |
| POST |
| PRI |
| PROPFIND |
| PROPATCH |
| PUT |
| REBIND |
| REPORT |
| SEARCH |
| TRACE |
| UNBIND |
| UNCHECKOUT |
| UNLINK |
| UNLOCK |
| UPDATE |
| UPDATEREDIRECTREF |
| VERSION-CONTROL |
- HTTP Headers
The header information to be sent by TR7 during requests to the services can be entered manually.
- HTTP Body
The HTTP body to be sent by TR7 during requests to the services can be entered manually.
- Expected Status Codes
The status code(s) expected to be returned by the service during the trigger are selected. Multiple selections can be made.
- The Complete List of HTTP Status Codes Supported by TR7
| Status Code | Status | Description |
|---|---|---|
| 100 | Informational | Continue |
| 101 | Informational | Switching Protocols |
| 102 | Informational | Processing |
| 103 | Informational | Early Hints |
| 200 | Successful | OK |
| 201 | Successful | Resource Created on Server |
| 202 | Successful | Accepted, not yet processed |
| 203 | Successful | Modified 200 OK Response |
| 204 | Successful | No Content |
| 205 | Successful | Reset Content |
| 206 | Successful | Partial Content |
| 207 | Successful | Multi-Status |
| 208 | Successful | Already Reported |
| 226 | Successful | IM Used |
| 300 | Redirection | Multiple Choices |
| 301 | Redirection | Moved Permanently |
| 302 | Redirection | Moved Temporarily |
| 303 | Redirection | GET Request Redirect |
| 304 | Redirection | Not Modified |
| 305 | Redirection | Use Server Proxy |
| 306 | Redirection | Unused (Previously "Switch Proxy") |
| 307 | Redirection | Temporary Redirect |
| 308 | Redirection | Permanent Redirect |
| 400 | Client Error | Bad Request |
| 401 | Client Error | Unauthorized |
| 402 | Client Error | Payment Required |
| 403 | Client Error | Forbidden |
| 404 | Client Error | Not Found |
| 405 | Client Error | Method Not Allowed |
| 406 | Client Error | Not Acceptable |
| 407 | Client Error | Proxy Authentication Required |
| 408 | Client Error | Request Timeout |
| 409 | Client Error | Conflict |
| 410 | Client Error | Gone |
| 411 | Client Error | Length Required |
| 412 | Client Error | Precondition Failed |
| 413 | Client Error | Payload Too Large |
| 414 | Client Error | URI Too Long |
| 415 | Client Error | Unsupported Media Type |
| 416 | Client Error | Range Not Satisfiable |
| 417 | Client Error | Expectation Failed |
| 418 | Client Error | 418 |
| 419 | Client Error | 419 |
| 420 | Client Error | Method Failure |
| 421 | Client Error | Misdirected Request |
| 422 | Client Error | Unprocessable Entity |
| 423 | Client Error | Locked |
| 424 | Client Error | Failed Dependency |
| 425 | Client Error | Too Early |
| 426 | Client Error | Upgrade Required |
| 428 | Client Error | Precondition Required |
| 429 | Client Error | Too Many Requests |
| 430 | Client Error | Request Header Fields Too Large (Shopify) |
| 431 | Client Error | Request Header Fields Too Large |
| 440 | Client Error | Session Time-out |
| 444 | Client Error | No Response |
| 449 | Client Error | Retry With |
| 450 | Client Error | Blocked by Windows Parental Controls |
| 451 | Client Error | Unavailable For Legal Reasons |
| 460 | Client Error | 460 |
| 463 | Client Error | 463 |
| 494 | Client Error | İstek Request Header Too Large |
| 495 | Client Error | SSL Certificate Error |
| 496 | Client Error | SSL Certificate Required |
| 497 | Client Error | HTTP Request Sent to HTTPS Port |
| 498 | Client Error | Invalid Token (Esri) |
| 499 | Client Error | Client Closed Request (Nginx) |
| 500 | Server Error | Internal Server Error |
| 501 | Server Error | Not Implemented |
| 502 | Server Error | Bad Gateway |
| 503 | Server Error | Service Unavailable |
| 504 | Server Error | Gateway Timeout |
| 505 | Server Error | HTTP Version Not Supported |
| 506 | Server Error | Variant Also Negotiates |
| 507 | Server Error | Insufficient Storage |
| 508 | Server Error | Loop Detected |
| 509 | Server Error | Bandwidth Limit Exceeded (Apache Web Server/cPanel) |
| 510 | Server Error | Not Extended |
| 511 | Server Error | Network Authentication Required |
| 520 | Server Error | Web Server Returned an Unknown Error |
| 521 | Server Error | Web Server Is Down |
| 522 | Server Error | Connection Timed Out |
| 523 | Server Error | Origin Is Unreachable |
| 524 | Server Error | A Timeout Occurred |
| 525 | Server Error | SSL Handshake Failed |
| 526 | Server Error | Invalid SSL Certificate |
| 529 | Server Error | Site is Overloaded |
| 530 | Server Error | Site is Frozen |
| 598 | Server Error | Network Read Timeout Error |
| 599 | Server Error | Network Connect Timeout Error |
- Expected Content Query
If there is an expected content query from the service during the trigger, the relevant query is entered.
- Add
Clicking the Add button adds the Trigger Action.