Skip to main content

Knowledge base

Pingara help center: set up
monitors, alerts and status pages

Step-by-step guides for site owners, developers and ops teams. Add your first monitor, decide who gets alerted and when, publish a status page, and connect Pingara to the tools you already use.

Quick Start Guide

Get started with Pingara in minutes. Create your account, add your first monitor, and understand your monitoring results.

4 min read

Setting Up Alerts

Learn how to create alert policies, configure notification rules, and ensure your team is always informed when monitors detect issues.

6 min read

Creating Status Pages

Build public status pages for your services with custom branding, monitor selection, and incident history. Keep your users informed with transparent uptime communication.

5 min read

Developer API

Authenticate, create and manage monitors, acknowledge incidents, and read uptime, checks, status page state, and the audit log from Pingara programmatically using the v1 REST Developer API.

36 min read

Browse by category

Understanding the Dashboard

Learn what every metric, chart, and indicator means on your Pingara dashboard. Master uptime percentages, Apdex scores, latency charts, and incident tracking.

Getting Started
6m

Creating Your First Monitor

Step-by-step guide to configuring your first uptime monitor in Pingara. Learn about URL format, check intervals, regions, status codes, keyword checks, and SSL tracking.

Getting Started
8m

Plans and Pricing

Compare Pingara Free and Pro plans. Understand monitor limits, check intervals, team features, data retention, and how to upgrade your subscription.

Getting Started
5m

HTTP/HTTPS Monitoring

Comprehensive guide to HTTP and HTTPS uptime monitoring in Pingara. Configure GET/POST/HEAD methods, expected status codes, custom headers, keyword checks, SSL certificate tracking, and redirect handling.

Monitors
8m

DNS Record Monitoring

Watch a DNS record for changes: confirm a domain still resolves, or alert when MX, TXT, NS or CAA records stop matching the values you expect.

Monitors
6m

WebSocket Monitoring

Check that a WebSocket endpoint completes a real RFC 6455 handshake, and optionally that the application behind it replies to a message you send.

Monitors
5m

Can't find your answer? Contact support