Health Checks

- 1 (Information to be Displayed in the Table)

Select which information will be displayed in the table listing Health Check Profiles.
The information that can be selected and is selected by default includes;

• Name
• Period
• Required Successes
• Check type
• Timeout
• Required Failures

- 2 (Add)

By clicking the Add button, a form for creating a new Health Check Profile opens.

- 3 (Delete)

By selecting one or more Health Check Profiles and clicking the Delete button, the relevant Health Check Profiles are deleted from the TR7 ASP device.

- 4 (Edit)

By clicking the Edit button, the editing screen of the relevant Health Check Profile opens.

- 5 (Search)

Used to search for all expressions in the table.

- 6 (RegExp Search)

Used to regexp search for all expressions in the table.

- 7 (Column Based Search)

Used to column based search for all expressions in the table.

- 8 (Usage Filter)

Used to filter which vServices all expressions in the table are used in.

- 9 (Page Information)

Information about how many Health Check Profiles are in the opened list and how many Health Check Profiles are listed is available. When Health Check Profiles are selected for deletion from the left side, the information of the selected Health Check Profile is displayed here.

- 10 (Page Size)

Selects the maximum number of Health Check Profiles to be listed in the opened list. Page transitions can be made with arrow icons between pages.

- Preview of the Selected HC Profile

After following the steps "Traffic Manager > Profiles > Health Checks" when any profile is clicked on, a window opens on the right side of the screen containing information related to that profile.

In this window, in addition to the information related to the selected profile, information about where the Health Check Profile is "Used In" also provided. It can be seen where the selected Health Check Profile is used in which Backend Services and in which Backend Services within the vService.

By clicking the (x) button in the upper right corner of the opened window, the preview can be closed.

- Name

Enter a name for the Health Check Profile to be created.

- Check Type

Select TCP.

- Expect Negative Result

It is checked whether the value of the created health check profile is negative or not. For example, if TCP health check is added and Expect Negative Result is checked, the health check is considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines at what intervals (in seconds) Backend Services will be checked.

- Timeout

The timeout limit should be a value between 0.01 and 3600. It is determined in seconds for the health check to be considered unsuccessful during the health check.

- TCP Scenario

It is used to perform TCP health checks scenario-based. The result of the health check is determined by controlling the information sent and received during the health check.

- Required Successes

Healthy response should be a value between 1 and 10. The number of successful responses required for services to be considered healthy is determined.

- Required Failures

Failed response should be a value between 1 and 10. The number of failed responses required for services to be considered unhealthy is determined.

- Add

By clicking the Add button, the Health Check Profile is added.

- Name

Enter a name for the Health Check Profile to be created.

- Check Type

Select Ping.

- Expect Negative Result

It is checked whether the value of the created health check profile is negative or not. For example, if Ping health check is added and Expect Negative Result is checked, the health check is considered successful when the ping response cannot be received.

- Period

The period should be a value between 0.5 and 3600. It determines at what intervals (in seconds) Backend Services will be checked.

- Timeout

The timeout limit should be a value between 0.01 and 3600. It is determined in seconds for the health check to be considered unsuccessful during the health check.

- Required Successes

Healthy response should be a value between 1 and 10. The number of successful responses required for services to be considered healthy is determined.

- Required Failures

Failed response should be a value between 1 and 10. The number of failed responses required for services to be considered unhealthy is determined.

- Add

By clicking the Add button, the Health Check Profile is added.

- Name

Enter a name for the Health Check Profile to be created.

- Check Type

Select HTTP.

- Expect Negative Result

Check whether the value of the created health check profile is negative or not. For example, if an HTTP health check is added, and Expect Negative Result is checked, the health check is considered successful when the HTTP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines at what intervals (in seconds) Backend Services will be checked.

- Timeout

The timeout limit should be a value between 0.01 and 3600. It is determined in seconds for the health check to be considered unsuccessful during the health check.

- Path + Query

Enter the Path + Query information for which the Backend Service will make requests. If left blank, requests are made to the root (/).

- Method

Select the HTTP method with which the health check will be performed.

- List of HTTP Methods Supported by TR7

- HTTP Headers

Manually enter header information to be sent by TR7 when making requests to the Backend Service.

- HTTP Body

Manually enter the HTTP body to be sent by TR7 when making requests to the Backend Service.

- Expected Status Codes

Select the status code(s) expected to be returned by the Backend Service during the health check. Multiple selections can be made.

- Complete List of HTTP Status Codes Supported by TR7

- Expected Content Query

If there is an expected content query by the Backend Service when performing health checks, the relevant query is written.

- Virtual Domain

If the health check needs to be performed over a domain name (host header information), the domain name information is entered.

- Required Successes

The healthy response should be a value between 1-10. The number of successful responses required for services to be considered healthy is determined.

- Required Failures

The failed response should be a value between 1-10. The number of failed responses required for services to be considered not healthy is determined.

- Add

By clicking the Add button, a Health Check Profile is added.

- Name

Enter a name for the Health Check Profile to be created.

- Check Type

Select HTTPS.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if a TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when TCP connection cannot be established.

- Period

The period should be a value between 0.5-3600. It determines at what interval (in seconds) the Backend Services will be checked.

- Timeout

The timeout limit should be a value between 0.01-3600. It specifies the maximum waiting time in seconds for a health check to be considered unsuccessful.

- Path + Query

Enter the Path + Query information for the Backend Service to make requests. If left blank, requests will be made to the root ("/").

- Method

Select the HTTP method with which the health check will be performed.

- List of HTTP Methods Supported by TR7

- HTTP Headers

When making a request to the Backend Service, header information to be sent by TR7 can be entered manually.

- HTTP Body

When making a request to the Backend Service, the HTTP body can be entered manually by TR7.

- Expected Status Codes

Select the status code(s) expected to be returned by the Backend Service during health checks. Multiple selections can be made.

- List of All HTTP Status Codes Supported by TR7

- Expected Content Query

When conducting health checks, if there is an expected content query by the vService, the relevant query is written.

- Virtual Domain

If the health check needs to be performed over a domain name (host header information), the domain name information is entered.

- Required Successes

The healthy response should be a value between 1-10. The number of successful responses required for services to be considered healthy is determined.

- Required Failures

The failed response should be a value between 1-10. The number of failed responses required for services to be considered not healthy is determined.

- Add

By clicking the "Add" button, a Health Check Profile is added.

- Name

Enter the name for the Health Check Profile to be created.

- Check Type

Select DNS.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines how often the Backend Services will be checked in seconds (s).

- Timeout

The timeout limit should be a value between 0.01 and 3600. It specifies the maximum waiting time in seconds (s) for a failed health check during the health check process.

- Query

Enter the domain name query information to be sent to the DNS server.

- Required Successes

The healthy response should be a value between 1 and 10. It defines the number of successful responses required for the services to be considered healthy.

- Required Failures

The failed response should be a value between 1 and 10. It defines the number of failed responses required for the services to be considered not working.

- Add

Click the Add button to add the Health Check Profile.

- Name

Enter the name for the Health Check Profile to be created.

- Check Type

Select FTP.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines how often the Backend Services will be checked in seconds (s).

- Timeout

The timeout limit should be a value between 0.01 and 3600. It specifies the maximum waiting time in seconds (s) for a failed health check during the health check process.

- FTP User

Enter the username information for logging into the FTP server.

- FTP Password

Enter the password information for logging into the FTP server.

- FTP Action

Select how the FTP health check operation will be performed.

- Required Successes

The healthy response should be a value between 1 and 10. It defines the number of successful responses required for the services to be considered healthy.

- Required Failures

The failed response should be a value between 1 and 10. It defines the number of failed responses required for the services to be considered not working.

- Add

Click the Add button to add the Health Check Profile.

- Name

Enter the name for the Health Check Profile to be created.

- Check Type

Select FTPS.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines how often the Backend Services will be checked in seconds (s).

- Timeout

The timeout limit should be a value between 0.01 and 3600. It specifies the maximum waiting time in seconds (s) for a failed health check during the health check process.

- FTP User

Enter the username information for logging into the FTPS server.

- FTP Password

Enter the password information for logging into the FTPS server.

- FTP Action

Select how the FTPS health check operation will be performed.

- Required Successes

The healthy response should be a value between 1 and 10. It defines the number of successful responses required for the services to be considered healthy.

- Required Failures

The failed response should be a value between 1 and 10. It defines the number of failed responses required for the services to be considered not working.

- Add

Click the Add button to add the Health Check Profile.

- Name

Enter the name for the Health Check Profile to be created.

- Check Type

Select LDAP.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines how often the Backend Services will be checked in seconds (s).

- Timeout

The timeout limit should be a value between 0.01 and 3600. It specifies the maximum waiting time in seconds (s) for a failed health check during the health check process.

- LDAP Authentication

LDAP Authentication is activated when health checks need to be performed by logging into the LDAP server. LDAP username and password information is entered for login control.

- Required Successes

The healthy response should be a value between 1 and 10. It defines the number of successful responses required for the services to be considered healthy.

- Required Failures

The failed response should be a value between 1 and 10. It defines the number of failed responses required for the services to be considered not working.

- Add

Click the Add button to add the Health Check Profile.

- Name

Enter the name for the Health Check Profile to be created.

- Check Type

Select LDAPS.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines how often the Backend Services will be checked in seconds (s).

- Timeout

The timeout limit should be a value between 0.01 and 3600. It specifies the maximum waiting time in seconds (s) for a failed health check during the health check process.

- LDAP Authentication

LDAP Authentication is activated when health checks need to be performed by logging into the LDAPS server. LDAP username and password information is entered for login control.

- Required Successes

The healthy response should be a value between 1 and 10. It defines the number of successful responses required for the services to be considered healthy.

- Required Failures

The failed response should be a value between 1 and 10. It defines the number of failed responses required for the services to be considered not working.

- Add

Click the Add button to add the Health Check Profile.

- Name

Enter a name for the Health Check Profile to be created.

- Check Type

Select Oracle.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines how often the Backend Services will be checked in seconds (s).

- Timeout

The timeout limit should be a value between 0.01 and 3600. It specifies the maximum waiting time in seconds (s) for a failed health check during the health check process.

- User

The username information to connect to the Oracle server is entered.

- Password

The password information of the user who will connect to the Oracle server is entered.

- Connection String

IP:Port/Path information to be connected to the Oracle server is entered.

- Oracle Scenario

It is used to perform Oracle health checks on a scenario-based basis. In scenarios, you can connect to the Oracle server and run commands. As a result of the commands run, the expected text and lines can be checked.

- Required Successes

The healthy response should be a value between 1 and 10. It defines the number of successful responses required for the services to be considered healthy.

- Required Failures

The failed response should be a value between 1 and 10. It defines the number of failed responses required for the services to be considered not working.

- Add

Click the Add button to add the Health Check Profile.

- Name

Enter a name for the Health Check Profile to be created.

- Check Tpye

Select Scenario.

- Expect Negative Result

Check whether the created health check profile is negative. For example, if TCP health check is added and "Expect Negative Result" is checked, the health check will be considered successful when the TCP connection cannot be established.

- Period

The period should be a value between 0.5 and 3600. It determines how often the Backend Services will be checked in seconds (s).

- Timeout

The timeout limit should be a value between 0.01 and 3600. It specifies the maximum waiting time in seconds (s) for a failed health check during the health check process.

- Scenario

Health check inspections on TR7 ASP devices can be performed on a scenario basis. Specific health checks can be performed on different paths at the same time within a single Backend Service, or more generally, TCP, Ping and HTTP health checks can be performed at the same time and checks can be carried out with and/or. Profiles previously added in health checks cannot be used in scenarios, and health checks defined within the scenario can only be used in scenario health checks. Period, Timeout, Required Successes and Required Failures checks are made only through the scenario. This information will not be checked in the health inspections that will be added.

- Required Successes

The healthy response should be a value between 1 and 10. It defines the number of successful responses required for the services to be considered healthy.

- Required Failures

The failed response should be a value between 1 and 10. It defines the number of failed responses required for the services to be considered not working.

- Add

Click the Add button to add the Health Check Profile.

Step > 1

First, follow the steps "Setting Mode > Traffic Manager > Backend Services" via the TR7 web interface.

Step > 2

On the screen that appears, right-click on the Backend Service to which the Health Check Profile will be added and select "Edit" or mark the relevant Backend Service on the left and click on the "Edit" button.

Step > 3

On the editing screen of the Backend Service, previously created profiles are displayed via the Health Check tab and the desired profile is selected. Additionally, a new Health Control profile can be added by clicking the Add button on the Backend Service editing screen.

Step > 4

By clicking the "Save" button, the changes made are saved and the health check of the Backend Service is checked.