Checks, locations & failure confirmation — found from sitemap — Checkly

Cited by

Facts read from this source

• Tcp payload assertions Report an error

  “Send a payload after the handshake and assert on what comes back: a PONG, a 220 banner, your own health string.”

• Tcp latency phases Report an error

  “Every run records DNS lookup, TCP connect, and data transfer separately, per location.”

• Tcp degraded failed thresholds Report an error

  “degradedResponseTime (default 4000 ms) marks a run degraded, maxResponseTime (default 5000 ms) fails it.”

• Tcp assertion types Report an error

  “Response time, with lessThan and greaterThan thresholds in milliseconds, and response data, with contains and notContains matches”

• Tcp should fail mode Report an error

  “Enable "this request should fail" on the monitor and connection failures such as timeouts and refused ports count as passed, while a successful connection still passes.”

• Tcp frequency range Report an error

  “From every 10 seconds to once every 24 hours, subject to the minimum interval on your plan.”

• Tcp public locations count Report an error

  “Monitors run from any of 22 public locations across the Americas, Europe, the Middle East, Africa, and Asia Pacific, or from private locations on your own infrastructure (Team and Enterprise plans).”

• Tcp port25 limitation Report an error

  “some public locations run on AWS, which blocks outbound port 25. Monitor SMTP on 587 or 465, or run the monitor from a private location.”

• Tcp retries Report an error

  “Retries with fixed, linear, or exponential backoff before an alert fires”

• Alert channels Report an error

  “Alerts to Slack, PagerDuty, Opsgenie, SMS, phone, webhooks, and more”

• Status page incidents Report an error

  “When a monitor fails you can open an incident on a Checkly status page automatically, so the people waiting on that service hear it from you first.”

• Private locations plans Report an error

  “Available on Team and Enterprise plans”

• Private locations agent architecture Report an error

  “One lightweight container, outbound-only connection to Checkly”

• Monitoring as code Report an error

  “The monitor is a TypeScript construct in your repo. Test it from CI, preview the deploy, apply it. Terraform and Pulumi providers cover the teams that live there instead.”

• Cli test deploy Report an error

  “npx checkly test runs the monitor once from a Checkly location and reports pass or fail in the terminal.”

• Per monitor model Report an error

  “TCP monitors are uptime monitors. Every plan includes a number of them: 10 on Hobby, 50 on Starter, 75 on Team, custom on Enterprise, with more available in blocks of 25. They are billed per monitor, not per run, so a 30-second schedule costs the same as a daily one.”

• Supported services Report an error

  “Anything that listens on a TCP port: Postgres, MySQL, and MongoDB databases, Redis, RabbitMQ and Kafka brokers, SMTP and IMAPS mail servers, FTP, SSH, and your own line-protocol services.”

• Related monitor types Report an error

  “For HTTP endpoints use a URL or API monitor, for DNS records a DNS monitor, and for plain host reachability an ICMP monitor.”

• Tcp data retention per run Report an error

  “Payload sent and response received, kept with every run”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.

Scores citing this record

• The Agency Developer Checks, locations & failure confirmation
• The Agency Developer Uptime reports, data & the vendor's own reliability
• The Agency Developer Pricing transparency
• The Customer Support Lead Checks, locations & failure confirmation
• The Customer Support Lead Uptime reports, data & the vendor's own reliability
• The E-Commerce Operations Manager Checks, locations & failure confirmation
• The SaaS Platform Engineer Checks, locations & failure confirmation
• The SaaS Platform Engineer Alerting, escalation & on-call
• The SaaS Platform Engineer Uptime reports, data & the vendor's own reliability
• The SaaS Platform Engineer Pricing transparency
• The Information Security Officer Checks, locations & failure confirmation
• The Information Security Officer Uptime reports, data & the vendor's own reliability
• The Skeptic Checks, locations & failure confirmation
• The Skeptic Pricing transparency