Environment Health
Loading environments…
Loading…
Fetching environments…
Incident Feed What do these mean?
Usage & Billing
Current billing cycle
Probe usage
Invoice history
On-Demand Services
Deep tests that run once on demand — beyond what the regular scheduled probes do
What are on-demand services?
Your regular scheduled probes write a small 4KB test file every 5–60 minutes to check connectivity and basic latency.
On-demand services go deeper — they stress test your filesystem, measure real throughput, and diagnose all your connectors at once.
Use them when you suspect a problem, before a production launch, or to investigate why a probe is showing degraded.
Branding & Alert Settings
Customise your portal and configure notification channels
Company details
Brand colour
Alert channels
Support
Choose the right channel for your issue — we respond faster based on severity
P1 — Critical incident 24/7
Production down, filesystem inaccessible, complete failure. ConnectWatch will have already sent you an alert — use this if you need immediate human help.
+91 98200 00001
Response: 15 min · Available 24×7×365
P2 — Technical support Business hrs
Degraded probes, latency spikes, connector config issues, SSH key problems, probe not running as expected.
+91 98200 00002
Mon–Fri 8am–8pm IST · Response: 2 hrs
General & billing Email
Invoices, plan upgrades, adding environments, onboarding new team members, feature requests.
support@connectwatch.io
Response within 4 business hours
Dedicated Slack channel Pro & Enterprise
Direct line to your account engineer. Ask questions, share screenshots, get config reviewed in real time.
#your-company-connectwatch
Not connected yet? Email support@connectwatch.io to get invited.
Before you contact support — self-serve fixes
Error message reference
Every error ConnectWatch shows with exact fix commands
What to do when a probe fails
Step-by-step runbooks for SSH, FS, HTTPS, and Degraded states
Filesystem probe setup guide
Server commands, permissions, SSH key setup
Run a diagnostic test now
On-Demand → Diagnostic probes all connectors immediately
Documentation
Guides, references and integration docs
New to ConnectWatch?
Open guide
Read How ConnectWatch works — what it probes, how incidents open, why it catches what other monitors miss. Takes 3 minutes to read.
Getting started
Quick start — onboard your first environment
Create an environment, add SSH credentials, run your first probe
Adding SSH credentials and endpoints
Private keys, passwords, host configuration — all connector types
Configuring HTTPS probe endpoints
Health check URLs, expected status codes, auth headers
Firewall rules — IPs to whitelist
Allow ConnectWatch to reach your servers on port 22
Setting up a dedicated probe user on your server
Isolated user with minimum permissions — recommended security practice
Probes & connectors
Connector guide — what each connector does
SSH, HTTPS, Filesystem, S3, Azure, GCS, SFTP, SMB, webhook
How the SSH probe works
What it connects to, what it uploads, what latency it measures
Filesystem latency probe — full setup guide
dd-based write/read/delete test, permissions, error reference
Large file throughput test
Segmented 1GB test, burst credit detection, I/O warnings
Status & alerts guide — what every badge means
OK, Degraded, Failed, Incident P1/P2 — causes and fixes
Connector marketplace
Add S3, Azure Blob, GCS, SharePoint, SMB connectors
Alerts & integrations
Email SMTP configuration
Gmail, Outlook, custom SMTP — step by step
Setting up Slack alerts
Create an incoming webhook and paste it into ConnectWatch
PagerDuty integration
Events API v2 — routing key setup, escalation policies
REST API reference
Endpoints, authentication, response formats
Billing & plans
Plan comparison — Starter, Pro, Enterprise
Probe intervals, environment limits, overage pricing
Understanding overage billing
How extra environments are charged, how to avoid surprises