TCP Check

Xitoring's TCP check enables users to monitor the availability and performance of TCP services by establishing a connection to the server. This monitoring method is essential for ensuring that critical network services are accessible and functioning properly.

The TCP check supports various configuration options, such as specifying the server's address and port. By providing these options, Xitoring's TCP check can effectively monitor TCP services and alert IT teams in real time if there are any issues, such as connection failures or slow response times. The ability to specify different ports enhances its effectiveness in monitoring a wide range of TCP services.

Create TCP Checks

Creating a TCP check in Xitoring can be done very easily by providing the following information to create the check and create a proper trigger for it.

Check Options

Type

From the list of available check types, TCP will be selected.

Related Server

As in Xitoring, there are Server checks and independent checks, you can Create a check and assign it to a Server so it will count as one of the checks of a specific server. this option also can be changed or edited later.

So the list will contain a list of registered servers that the user can assign the check to them.

Hostname

The hostname is the address of the TCP check, it can be an IPv4 or IPv6 address or a domain name, you can see examples of each of them in the following box:

IPv4
107.45.66.2

IPv6
fe80::a510:68bd:7405:1869

Domain
xitoring.com

Check Label

Users can choose a name for the check that is being created using this field, Check label can contain characters, space, and numbers. Special characters are not allowed in the check label section.

Port

Xitoring's TCP check allows users to monitor services that use different ports. Users can create separate checks for each port and configure them accordingly.

By creating multiple checks for different ports, users can ensure that all aspects of their TCP services are monitored thoroughly. Xitoring's TCP check provides comprehensive monitoring, including speed testing, ensuring that the service is functioning correctly and reliably.

String to Send

Users can specify a string to send to the TCP service. This string acts as a test message to which the server should respond appropriately. By sending this string, Xitoring can verify that the service is active and responding as expected.

Group

The next option is Group. Xitoring has an advanced Group/Sub-Group management system so users can sort and organize Checks and Server, For example, some users organize their assets based on location and create Groups for countries and Sub-Groups for Cities. it can help see the records for a specific part of your assets easily.

Using the gear icon next to the title, you can access the Group management mini tool, the user can create, delete and edit groups and sub-groups.

Interval

Interval sets how often probing nodes will make their requests to your URL. A 1-minute interval will provide the most detailed, accurate reports and notifications. Also, for some services, a higher interval makes more sense. You can configure Xitoring to check your TCP Check status every minute or adjust the interval as needed.

Trigger Options

The most important part of creating a check is Trigger options Triggers will define the incident status of a Check.

Notification Roles

In this section user can assign one or more notification roles to this check trigger, it will define who gets notified and how every time this check has an incident. For Example, the user has two notification roles one for the IT team that contains the Email and phone numbers of the team members, and one notification role for the CTO. Users can configure the trigger to notify the IT team and the CTO in time of an incident using Email and SMS notifications.

Fault Tolerance

Fault tolerance is a time value (Minutes) that determines how much stress can a system take before it's entering a critical state. If you set FT to 5 we send an incident report when the incident is existing for 5 minutes.

Response Time (ms)

Specify the acceptable response time in milliseconds. If the response time exceeds this threshold, an incident will be triggered.

Response Condition

Users can select a response condition to evaluate the server's response. The options include:

• No condition
• Should contain
• Should not contain
• Should contain all of
• Should contain at least one of
• Should not contain all of
• Should not contain at least one of

After selecting a condition, an "Expected Response" text field appears where users can specify the expected response. If the condition involves multiple criteria, the "Expected Response" field can accept multiple inputs.