Skip to main content

add ability for tcp checks.

Feature RequestCheck Types

💡 For general support requests and bug reports, please go to checklyhq.com/support

Is your feature request related to a problem? Please describe. We do http monitoring but we have some api's that are not http but are at tcp level. Having monitoring for tcp connections basic check on URL and any Port is great. Can integrate tls as well.

Describe the solution you'd like as part of addition of api checks, we can add tcp as an option in the drop down.

Describe alternatives you've considered using datadog right now .

Additional context Add any other context or screenshots about the feature request here.

original GH issue link https://github.com/checkly/public-roadmap/issues/96

Posted by Tim Nolet ·
Status: Completed4 comments

Log in to comment and vote

Comments4

  • Susanne Tünker

    •

    Jan 15, 2025

    Brief update on this feature request: TCP checks are now available for you to use in early access, see https://feedback.checklyhq.com/changelog/tcp-checks-are-here-in-early-access for more info.

  • Susanne Tünker

    •

    Nov 11, 2024

    Hi all! We’re now actively exploring and designing TCP checks, and would love to hear from you. If you’re open to a brief chat, I’d appreciate learning more about how you envision using TCP checks and any specific needs or ideas you have in mind. Your input would be incredibly helpful as we shape this feature—please reach out if you're interested!

  • kim.kraft@teamwass.com

    •

    Sep 28, 2023

    +1 on this request.

    As mentioned in the original GH issue, many of us are currently maintaining 2 or more monitoring providers and I am sure we would very much like to consolidate into Checkly. The lack of a basic HTTP or TCP check (with an appropriate price point) is preventing us from completely migrating our monitoring to Checkly.

    We currently use the API check for basic uptime monitoring on some of our environments, but the pricing for this check prevents us from fully adopting it as a solution.

    TCP as an option in the API checks is one approach but might complicate billing. I envisioned another check type being added to the existing Web, API and HeartBeat monitors, along with the appropriate TCPCheck construct for "monitoring as code."

    • Tim Nolet

      •

      Dec 20, 2023

      @kim.kraft@teamwass.com sorry for the late reply. I never got an email about this 🤔. I think we are aligned and want to introduce a TCPCheck construct just like you mentioned.