MonSpark Docs
  • 👋Welcome to MonSpark
  • Overview
    • 💡What Is Monitoring?
    • ✨Types of Monitoring
    • 🛠️Getting Started with MonSpark
  • Fundamentals
    • 🔔Alerting
      • 📒Integrations
      • 🚨Escalation Policies
    • ⚠️Incidents
    • 📣Status Pages
    • 🏅Summary
    • 🔍Auto Discovery
  • Website Monitoring
    • 💻What is Website Monitoring?
    • 🛠️Getting started with Website Monitoring
    • ⚙️Working With Monitors
      • ⏯️Pausing/Resuming Monitors
      • 🗑️Deleting Monitors
      • 💠Bulk Create
      • 📄Reporting
    • 📈Availability
      • Uptime Monitor
        • Uptime Monitor Create
        • Understanding Uptime Monitor Details
      • Ping Monitor
        • Ping Monitor Create
      • TCP Monitor
        • TCP Monitor Create
    • 🛡️Security
      • Domain Expiration Monitor
        • Domain Expiration Monitor Create
      • DNS Record Monitor
        • DNS Record Monitor Create
      • IP Blacklist Monitor
        • IP Blacklist Monitor Create
      • Whois Monitor
        • Whois Monitor Create
      • Subdomain Monitor
        • Subdomain Monitor Create
      • Port Discovery Monitor
        • Port Discovery Monitor Create
    • ✨SEO
      • Lighthouse Audits
        • Lighthouse Monitor Create
      • Sitemap Monitor
        • Sitemap Monitor Create
      • URL Monitor
        • URL Monitor Create
    • ⛓️Integrity
      • Text Monitor
        • Text Monitor Create
      • Screenshot Monitor
        • Screenshot Monitor Create
      • Cookie Monitor
        • Cookie Monitor Create
      • Technology Monitor
        • Technology Monitor Create
      • Source Code Monitor
        • Source Code Monitor Create
    • 🕐Cronjob Monitoring
  • Server Monitoring
    • 🖥️What is Server Monitoring?
    • 🛠️Getting Started with Server Monitoring
      • 🖥️Servers
      • ⏰Alarms
      • 🗃️Rules
  • Transaction Monitoring
    • 🔮What is Transaction Monitoring?
  • Extras
    • ⛑️Troubleshooting and Support
      • IP Whitelisting
    • ⁉️FAQs
    • 💬Appendix
Powered by GitBook
On this page
  • Create a TCP Monitor with just 3 clicks
  • TCP Monitor Configurations
  • General Settings
  • Request Settings
  • Notification Settings

Was this helpful?

  1. Website Monitoring
  2. Availability
  3. TCP Monitor

TCP Monitor Create

PreviousTCP MonitorNextSecurity

Last updated 1 year ago

Was this helpful?

Create a TCP Monitor for your preferred port of the domain name/IP address. Configure them according to your needs, if needed.

Create a TCP Monitor with just 3 clicks

  • Click the "Create Monitor" button on the right side of the page.

  • Find the "TCP Monitoring" feature and click on the "Create TCP Monitor" button.

  • Type your preferred domain name or IP address, and the port that you want to monitor.

  • Lastly, click on "Create TCP Monitor" and your monitor is ready.

While it's just as simple as that, we have tons of configurations we can apply to our monitors to get the best monitoring experience. Most of the time, default configurations will work fine, but sometimes you may need to adjust a few to fit your specific needs.

TCP Monitor Configurations

General Settings

Host

The domain name or the IP address of the website you want MonSpark to monitor.


Port

The specific port of the provided host.


Name of check

The monitor name is used to identify this specific monitor and is also utilized in notifications.


Check Interval

Determines the frequency of monitoring checks.


Tags

Used to categorize monitors for future grouping, you can either choose from existing tags or create new ones.


Request Settings

Location

Determines the location from which MonSpark monitors the provided URL/IP address.


Timeout

The timeout value for monitoring requests defines the duration within which the website must respond.


Confirmation Count

The confirmation count specifies the number of failed consecutive monitoring requests needed for the monitor to be marked as down.

Please keep in mind that these two configurations go hand in hand when determining how long your service needs to be unreachable for it to be considered down. For example, 30-second timeout and 3 checks mean that the monitor will be marked as down if it remains unreachable for 90 seconds.


Use Secure Connection

Enabling this option will enforce the monitoring checks to utilize the secure connection.


Host Name

If you've entered an IP address above as the target host and activated the secure connection option, you need to specify the target host domain to establish a secure connection


Custom DNS

Sets the preferred DNS server for resolving the IP address of the target URL.


Text to expect

If the provided text is not found within the response, the monitor will be marked as down.


Text to not expect

If the provided text is found within the response, the monitor will be marked as down.


Text to send

The provided text will send within the monitoring request.


Notification Settings

Escalation Policies

Determines the escalation policies that will be applied to the monitor.

📈