inostop Logo NavBack to create monitor

Monitor Usage Guide

This page explains how to configure Login and API monitors and common pitfalls.

Login Monitor

  1. Login monitor requires a credential; target will follow the credential login URL.
  2. Fields: name, login URL (http/https), method (POST/GET), username, password, optional headers JSON; default body uses username/password placeholders with form encoding.
  3. Success rule: status code defaults to 2xx/3xx and (if set) response body contains success keyword; otherwise it fails and triggers alert.
  4. Interface-level login check only; cannot handle captcha/image verification/SMS OTP flows. Captcha pages will be treated as failure.
  5. Tip: set headers (e.g., {"User-Agent":"inostop-monitor","X-Env":"prod"}) when token/UA is required.

API Monitor

  1. Target must be full API URL (with scheme), supports GET/POST/PUT/DELETE.
  2. Success rule: defaults to HTTP 2xx/3xx (does not read JSON code field); if expected status codes are set, uses that list.
  3. Optional success keyword: if set, response body must contain the text (reads up to 1MB) in addition to the status rule.
  4. Note: does not inspect JSON business fields (e.g., {"code":200}); only HTTP status + optional keyword are used.
  5. Result records status and latency; alerts include failure reasons (timeout, status code, keyword not matched, etc.).
  6. Use headers for simple auth (Token/Basic); add “Success keyword” if the response must contain specific text.

Domain Monitor

  1. Target is a bare domain (no scheme); checks expiry and reachability; frequency: 24h or 7d.
  2. Shows last check time/status/latency; expiry <30/7/5 days triggers alerts per settings.

SSL Monitor

  1. Target is HTTPS domain/URL; checks cert expiry and issuer; frequency: 24h or 7d.
  2. Expiry thresholds (30/7/5 days) trigger alerts; result shows expiry and last/ recent check time.

Web Monitor

  1. Target is full URL; records status code and page load time, captures PC/Mobile screenshots and resource timing.
  2. Alert threshold: page load time (e.g., 500/1000/2000/3000ms); screenshot time recorded separately, not in page load.

Ping Monitor

  1. Target can be domain or IP; frequency 5/15/60 minutes; timeout configurable.
  2. Records latency and failure reason (timeout/unreachable); alerts on failure.

Telnet Monitor

  1. Target is domain/IP with port; frequency 5/15/60 minutes; timeout configurable.
  2. Checks port connectivity; records latency and failure reason (refused/timeout etc.); alerts on failure.

FAQ

  1. record not found: linked credential deleted or belongs to another user, reselect/create a credential.
  2. No screenshot: Login monitor does not capture screenshots; use Web monitor instead.
  3. Web screenshots may use different sources per language; if an image fails to open, try switching language.

Need help? Contact Telegram support:

Open Telegram Support