Health Checks
About
Health checks are performed by TR7 GTM to verify whether DNS records are healthy. TR7 GTM provides health checks for DNS records using methods such as HTTP, Scenario, Datacenter, TCP, Ping, Oracle, and others. Based on the results of the health checks, it is possible to manage which response will be returned or from which data center the response will come when a DNS record is queried.
How to Add?
To add a new Health Check, navigate through the TR7 ASP web interface: Global Traffic Manager (GTM) > Settings > Health Checks > Add. In the opened screen, a new Health Check can be defined.
Interface
Health Checks Listing Screen
The list of all Health Checks added to the TR7 ASP device can be accessed by following "Global Traffic Manager (GTM) > Settings > Health Checks". On this screen, Health Checks can be added, edited, and deleted.
- 1 (Information to be Displayed in the Table)
The information to be displayed in the table containing the Health Checks list is selected.
The selectable information, which is selected by default, includes;
- Status
- Check Type
- Name
- 2 (Add)
Clicking the Add button opens the form to add a new Health Check.
- 3 (Edit)
Clicking the Edit button opens the editing screen for the relevant Health Check.
- 4 (Delete)
One or more Health Checks can be selected, and by clicking the Delete button, the relevant Health Checks are deleted from the current 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 Health Check profiles and how many are listed on the current page.
- 9 (Page Size)
Allows selecting the maximum number of Health Check profiles displayed per page. Arrows can be used to navigate between pages.
- 10 (Information to be Displayed in the Automatic Health Checks Table)
The information to be displayed in the Health Checks table automatically created by TR7 GTM can be selected.
The selectable information, which is selected by default, includes;
- Status
- Check Type
- Name
- 11 (Default Automatic Health Checks)
The default automatic Health Checks are as follows;
- Always: Used for a DNS record or Datacenter that is considered healthy under all conditions and at all times, and for which health checks are not required.
- Never: Used for a DNS record or Datacenter that is considered unhealthy under all conditions and at all times, and for which health checks are not required.
- (local) has internet access: Health check for the internet access of the TR7 device in the local data center.
- (local) is under maintenance: Health check for the TR7 device being in maintenance mode in the local data center.
- 12 (Search)
Used to search all expressions in the table.
- 13 (RegExp Search)
Used to search all expressions in the table using regular expressions.
- 14 (Column Based Search)
Used to search all expressions column-based.
- 15 (Page Information)
Displays the total number of Health Check profiles and how many are listed on the current page.
- 16 (Page Size)
Allows selecting the maximum number of Health Check profiles displayed per page. Arrows can be used to navigate between pages.
- 17 (Added Automatic Health Checks)
The health checks automatically added after the configuration are as follows:
- Always: Used for a DNS record or Datacenter that is considered healthy under all conditions and at all times, and for which health checks are not required.
- Never: Used for a DNS record or Datacenter that is considered unhealthy under all conditions and at all times, and for which health checks are not required.
- (local) has internet access: Health check for the internet access of the TR7 device in the local data center.
- (local) is under maintenance: Health check for the TR7 device being in maintenance mode in the local data center.
- WAN access to DRC is successful: Health check for WAN access to the TR7 device in the added remote data center.
- LAN access to DRC is successful: Health check for LAN access to the TR7 device in the added remote data center.
- Access to DRC is successful: Health check for access to the TR7 device in the added remote data center.
- DRC has internet access: Health check for the internet access of the TR7 device in the added remote data center.
- DRC is under maintenance: Health check for the TR7 device being in maintenance mode in the added remote data center.
Warning
Changes to the default health checks automatically added based on the configurations can be viewed.
- Preview of Selected Health Check
After following the steps "Global Traffic Manager (GTM) > Settings > Health Checks", clicking on any Health Check opens a window on the right side of the screen containing the information related to that Health Check.
Interface
Datacenter HC > Health Check Addition Form
A new Health Check is added to the TR7 ASP device by following the steps "Global Traffic Manager (GTM) > Settings > Health Checks > Add".
- Name
The name of the Health Check to be created is entered.
- Check Tpye
Datacenter HC is selected.
- Expect Negative Result
The inverse of the created health check profile is checked. For example, if a TCP health check is added and Expect Negative Result is marked, the health check is considered successful when the TCP connection cannot be established.
- Datacenter
The TR7 device in the data center where the Health Check will be performed is selected.
- Datacenter HC Type
The information to be checked in the selected data center for the Health Check to be created is selected.
By selecting CPU Usage, the CPU usage of the selected data center is monitored as part of the health check.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting BW (Bandwidth), the bandwidth of the selected data center is monitored as part of the health check.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting Up Services, the number of up vServices in the selected data center is monitored as part of the health check.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting Down Services, the number of down vServices in the selected data center is monitored as part of the health check.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting vService Status, the status of the vService in the selected data center is monitored as part of the health check.
The name of the vService to be monitored for health check in the relevant data center is selected.
It is recommended to leave the selected vService ID as the default.
By selecting vService Status, the health check is performed based on the number of sessions of the vService in the selected data center.
The name of the vService to be monitored based on the session count in the relevant data center is selected.
It is recommended to leave the selected vService ID as the default.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting vService Request Per Second, the health check is performed based on the number of requests per second for the vService in the selected data center.
The name of the vService to be monitored based on the requests per second in the relevant data center is selected.
It is recommended to leave the selected vService ID as the default.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting vService Connections, the health check is performed based on the number of connections for the vService in the selected data center.
The name of the vService to be monitored based on the number of connections in the relevant data center is selected.
It is recommended to leave the selected vService ID as the default.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting vService CPU Usage, the health check is performed based on the CPU usage of the vService in the selected data center.
The name of the vService to be monitored based on CPU usage in the relevant data center is selected.
It is recommended to leave the selected vService ID as the default.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
By selecting vService BW, the health check is performed based on the bandwidth of the vService in the selected data center.
The name of the vService to be monitored based on bandwidth usage in the relevant data center is selected.
It is recommended to leave the selected vService ID as the default.
By selecting the Less Than operator, the condition is triggered when the given value is smaller than the specified threshold.
By selecting the Equals To operator, the condition is triggered when the given value is equal to the specified value.
By selecting the Greater Than operator, the condition is triggered when the given value is greater than the specified threshold.
By selecting the Range operator, the condition is triggered when the given value falls within the specified range.
- Required Successes
A healthy response should be a value between 1 and 10. The required number of successful responses for the services to be considered healthy is determined.
- Required Failures
A failed response should be a value between 1 and 10. The required number of failed responses for the services to be considered unhealthy is determined.
- Add
By clicking the Add button, the Health Check is added.
TCP > Health Check Addition Form
By following the steps "Global Traffic Manager (GTM) > Settings > Health Checks > Add", a new Health Check is added to the TR7 ASP device.
- Name
The name for the Health Check to be created is entered.
- Check Type
TCP is selected.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
The negation of the created Health Check is verified. For example, if a TCP Health Check is added and Expect Negative Result is selected, the health check will be considered successful when the TCP connection cannot be established.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- Allow Half Open TCP Connections
- TCP Scenario
It is used for scenario-based TCP health checks. The sent information and the information in the response are checked to determine the result of the health check.
A request is made using the Telnet protocol. The first line contains the HTTP request line, and the following lines contain the HTTP request header information. After the last piece of information entered, two blank lines should be left by pressing ENTER.
The response body returned from the server is checked. The presence of the written text within the response body is checked.
The response body returned from the server is checked using Regex.
The scenario waits for the specified amount of time before the process is executed.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, the Health Check is added.
Ping > Health Check Addition Form
By following the steps "Global Traffic Manager (GTM) > Settings > Health Checks > Add", a new Health Check is added to the TR7 ASP device.
- Name
The name for the Health Check to be created is entered.
- Check Type
Ping is selected.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
The negation of the created Health Check is verified. For example, if a TCP Health Check is added and Expect Negative Result is selected, the health check will be considered successful when the TCP connection cannot be established.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
HTTP > Sağlık Denetimi Profili Ekleme Formu
"Global Traffic Manager (GTM) > Settings > Health Checks > Add" adımları takip edilerek TR7 ASP cihazı üzerine yeni bir Sağlık Denetim Profili eklenir.
- Name
The name for the Health Check to be created is entered.
- Check Type
HTTP seçilir.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
Oluşturulan sağlık denetimi profilinin değili kontrol edilir. Örnek olarak TCP sağlık denetimi eklenip Expect Negative Result işaretlenirse, TCP bağlantısı kurulamadığı zaman sağlık denetimi başarılı sayılmış olur.
- Period
The period must be a value between 0.5 and 3600 seconds. It determines how frequently the Institution Services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- Path + Query
Kurum Servisinin istek yapılacağı Path + Query bilgisi girilir. Boş bırakıldığı taktirde istekler / (köke) yapılır.
- Method
Sağlık denetiminin hangi HTTP metodu ile yapılacağı seçilir.
- TR7 Tarafından Desteklenen HTTP Metotlarının Listesi
| 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
Kurum Servisine istek yapılırken TR7 tarafından gönderilecek başlık bilgileri manuel olarak girilebilir.
- HTTP Body
Servislere istek yapılırken TR7 tarafından gönderilecek HTTP gövdesi (body) manuel olarak girilebilir.
- Expected Status Codes
Sağlık denetimi yapılırken servis tarafından dönmesi beklenen durum kodu/kodları seçilir. Birden fazla seçim yapılabilir.
- TR7 Tarafından Desteklenen HTTP Durum Kodlarının Tüm Listesi
| 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
Sağlık denetimi yapılırken servis tarafından beklenen bir içerik sorgusu varsa ilgili sorgu yazılır.
- Virtual Domain
Sağlık denetiminin alan adı (host başlık bilgisi) üzerinden yapılması gerekiyor ise alan adı bilgisi girilir.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
HTTPS > Sağlık Denetimi Profili Ekleme Formu
By following the steps "Global Traffic Manager (GTM) > Settings > Health Checks > Add", a new Health Check is added to the TR7 ASP device.
- Name
The name for the Health Check to be created is entered.
- Check Type
HTTPS seçilir.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
Oluşturulan sağlık denetimi profilinin değili kontrol edilir. Örnek olarak TCP sağlık denetimi eklenip Expect Negative Result işaretlenirse, TCP bağlantısı kurulamadığı zaman sağlık denetimi başarılı sayılmış olur.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- Path + Query
Kurum Servisinin istek yapılacağı Path + Query bilgisi girilir. Boş bırakıldığı taktirde istekler / (köke) yapılır.
- Method
Sağlık denetiminin hangi HTTP metodu ile yapılacağı seçilir.
- TR7 Tarafından Desteklenen HTTP Metotlarının Listesi
| 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
Kurum Servisine istek yapılırken TR7 tarafından gönderilecek başlık bilgileri manuel olarak girilebilir.
- HTTP Body
Kurum Servisine istek yapılırken TR7 tarafından gönderilecek HTTP gövdesi (body) manuel olarak girilebilir.
- Expected Status Codes
Sağlık denetimi yapılırken Kurum Servisi tarafından dönmesi beklenen durum kodu/kodları seçilir. Birden fazla seçim yapılabilir.
- TR7 Tarafından Desteklenen HTTP Durum Kodlarının Tüm Listesi
| 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
Sağlık denetimi yapılırken Kurum Servisi tarafından beklenen bir içerik sorgusu varsa ilgili sorgu yazılır.
- Virtual Domain
Sağlık denetiminin alan adı (host başlık bilgisi) üzerinden yapılması gerekiyor ise alan adı bilgisi girilir.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
DNS > Sağlık Denetimi Profili Ekleme Formu
"Global Traffic Manager (GTM) > Settings > Health Checks > Add" adımları takip edilerek TR7 ASP cihazı üzerine yeni bir Sağlık Denetim Profili eklenir.
- Name
The name for the Health Check to be created is entered.
- Check Type
DNS seçilir.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
Oluşturulan sağlık denetimi profilinin değili kontrol edilir. Örnek olarak TCP sağlık denetimi eklenip Expect Negative Result işaretlenirse, TCP bağlantısı kurulamadığı zaman sağlık denetimi başarılı sayılmış olur.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- Query
DNS sunucusuna yapılacak olan alan adı (domain) sorgu bilgisi girilir.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
FTP > Sağlık Denetimi Profili Ekleme Formu
"Global Traffic Manager (GTM) > Settings > Health Checks > Add" adımları takip edilerek TR7 ASP cihazı üzerine yeni bir Sağlık Denetim Profili eklenir.
- Name
Oluşturulacak olan Sağlık Denetim Profiline isim girilir.
- Check Type
FTP seçilir.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
Oluşturulan sağlık denetimi profilinin değili kontrol edilir. Örnek olarak TCP sağlık denetimi eklenip Expect Negative Result işaretlenirse, TCP bağlantısı kurulamadığı zaman sağlık denetimi başarılı sayılmış olur.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- FTP User
FTP sunucusuna giriş için kullanıcı adı bilgisi girilir.
- FTP Password
FTP sunucusuna giriş için kullanıcı adının şifre bilgisi girilir.
- FTP Action
FTP sağlık denetim işleminin nasıl yapılacağı seçilir.
FTP sunucusuna FTP User ve FTP Password sekmelerinde girilen bilgiler ile sadece giriş işlemi yapılır.
FTP sunucusuna FTP User ve FTP Password sekmelerinde girilen bilgiler ile giriş işlemi yapılır ve FTP Path sekmesinde girilen path bilgisi ile de ilgili dizin listelenir.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
FTPS > Sağlık Denetimi Profili Ekleme Formu
"Global Traffic Manager (GTM) > Settings > Health Checks > Add" adımları takip edilerek TR7 ASP cihazı üzerine yeni bir Sağlık Denetim Profili eklenir.
- Name
The name for the Health Check to be created is entered.
- Check Type
FTPS seçilir.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
The negation of the created Health Check is verified. For example, if a TCP Health Check is added and Expect Negative Result is selected, the health check will be considered successful when the TCP connection cannot be established.
- Period
The period must be a value between 0.5 and 3600 seconds. It determines how frequently the Institution Services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- FTP User
The username required for logging into the FTPS server is entered.
- FTP Password
The password for the FTPS server login is entered.
- FTP Action
The method for performing the FTPS health check is selected.
The FTP server login process is performed using the credentials entered in the FTP User and FTP Password fields.
The FTP server login process is performed using the credentials entered in the FTP User and FTP Password fields. Additionally, the directory specified in the FTP Path field is listed.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
LDAP > Sağlık Denetimi Profili Ekleme Formu
"Global Traffic Manager (GTM) > Settings > Health Checks > Add" adımları takip edilerek TR7 ASP cihazı üzerine yeni bir Sağlık Denetim Profili eklenir.
- Name
The name for the Health Check to be created is entered.
- Check Type
LDAP seçilir.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
The negation of the created Health Check is verified. For example, if a TCP Health Check is added and Expect Negative Result is selected, the health check will be considered successful when the TCP connection cannot be established.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- LDAP Authentication
LDAP sunucusuna giriş yapılarak sağlık denetimi yapılmak istenildiği durumlarda LDAP Authentication devreye alınır. Giriş kontrolü için LDAP kullanıcı adı ve şifre bilgisi girilir.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
LDAPS > Sağlık Denetimi Profili Ekleme Formu
By following the steps "Global Traffic Manager (GTM) > Settings > Health Checks > Add", a new Health Check is added to the TR7 ASP device.
- Name
The name for the Health Check to be created is entered.
- Check Type
LDAPS is selected.
- Expect Negative Result
The negation of the created Health Check is verified. For example, if a TCP Health Check is added and Expect Negative Result is selected, the health check will be considered successful when the TCP connection cannot be established.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- LDAP Authentication
LDAPS sunucusuna giriş yapılarak sağlık denetimi yapılmak istenildiği durumlarda LDAP Authentication devreye alınır. Giriş kontrolü için LDAPS kullanıcı adı ve şifre bilgisi girilir.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.
Oracle > Sağlık Denetimi Profili Ekleme Formu
By following the steps "Global Traffic Manager (GTM) > Settings > Health Checks > Add", a new Health Check is added to the TR7 ASP device.
- Name
The name for the Health Check to be created is entered.
- Check Type
Oracle seçilir.
- Address
The IP:Port information for the Health Check to be created is entered.
- vDevice
The virtual TR7 device through which the Health Check will be performed is selected.
- Route Table
The Route Table through which the added Health Check will be performed is selected. If no Route Table has been added, it should remain as DEFAULT. For detailed information about Route Tables, please click here.
- Expect Negative Result
Oluşturulan sağlık denetimi profilinin değili kontrol edilir. Örnek olarak TCP sağlık denetimi eklenip Expect Negative Result işaretlenirse, TCP bağlantısı kurulamadığı zaman sağlık denetimi başarılı sayılmış olur.
- Period
The period must be a value between 0.5 and 3600. This determines the interval (in seconds) at which the services will be checked.
- Timeout
The timeout limit must be a value between 0.01 and 3600 seconds. It defines the maximum waiting time in seconds before a health check is considered unsuccessful.
- User
The username information 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 the Oracle server to connect to is entered.
- Oracle Scenario
Scenario based Oracle health checks are used to connect to an Oracle server and execute commands. The results of the executed commands can be checked for expected text and lines.
- Required Successes
The healthy response value must be between 1 and 10. This value determines the number of successful responses required for the service to be considered operational.
- Required Failures
The unsuccessful response value must be between 1 and 10. This value determines the number of failed responses required for the service to be considered unhealthy.
- Add
By clicking the Add button, a Health Check Profile is added.