Skip to main content

Beat Types

Beat types describe what StatiBeat checks and what kind of signal the Beat produces.

Common first choices​

Start with the simplest Beat that proves the user-facing path works.

  • HTTP: checks a website, status page, or general web endpoint
  • API: checks a service endpoint with API-focused naming and messages
  • Latency: checks whether an endpoint is too slow
  • SSL / Certificate Check: checks certificate validity and expiry

These are good first choices for most teams.

Private and browser checks​

Use Private Beat when StatiBeat needs a small agent inside your network to check something the shared runtime cannot reach.

Use Browser Journey when a simple endpoint check is not enough and you need to verify a real user flow, such as sign-in, checkout, or signup.

Network checks​

Use network-focused Beats when the signal is lower-level:

  • TCP Connect: confirms a host and port accept connections
  • DNS Resolve: confirms a hostname resolves
  • ICMP Ping: checks basic reachability
  • Packet Loss: checks intermittent network quality

These are useful for infrastructure and edge-reachability checks, but they may need careful messaging before becoming customer-facing.

External Event​

Use External Event when another monitoring system already has the trusted signal.

External Event Beats are driven by External Beat Triggers instead of scheduled probes.

Generic Advanced​

Use Generic (Advanced) only when the simpler Beat types do not fit.

If you are unsure, start with a specific Beat type first. It will usually be easier for operators to understand later.