Miterl Guide

Introduction

Miterl is an uptime monitoring service designed for web agencies and development teams who manage multiple client websites and services. It provides site uptime monitoring, SSL and domain expiry tracking, automated incident detection and alerting, client-facing status pages, and monthly report generation — everything you need for ongoing operations and maintenance.

Simply create an account and start adding monitors to begin watching your sites immediately.

• Manage all your client sites from a single dashboard
• Get instant alerts via Slack, email, LINE, and more when issues occur
• Create branded status pages to share with your clients
• Automatically generate monthly reports to deliver to clients

Account Settings

From the top-right menu → Account Settings, you can update your email, password, company info, branding, time zone, and language. You can also delete your account.

What you can change

• Email address (a confirmation email is sent after change)
• Password
• Company info (billing address, legal name)
• Logo and accent color (applied to reports / status pages)
• Time zone and display language (Japanese / English)
• Account deletion (a confirmation dialog appears first)

Monitor Types

Miterl offers several monitor types to suit different use cases. Click "Add Monitor" from the dashboard and select the type you need.

Check intervals vary by plan: Free supports 5-minute intervals, Standard supports 3-minute intervals, and Pro supports intervals as short as 1 minute. HTTP and Keyword monitors also support optional Basic Auth (username / password).

Per-plan availability

Free covers HTTP / Ping / Heartbeat. Standard adds Keyword / SSL / TCP. Pro adds WHOIS / DOM Integrity on top. Upgrading unlocks the additional types automatically.

Bulk Action

Tick multiple monitors on the list view to pause, resume, tag, or delete them all at once. Handy for shifting groups of client monitors when contracts change.

CSV Import / Export

Bulk-add monitors via CSV from the list view. Download the template, fill in name / url / type / interval_seconds / failure_threshold / keyword / tags / sla_target_percent, and upload.

Existing monitors can also be exported to CSV — including computed fields like SSL days remaining and certificate expiry — useful as a backup before monthly client reports.

Rows whose URL+type combination already exists, or that exceed your plan limit, are skipped automatically. The result screen shows success / fail / skip counts with reasons.

Notification Channels

Configure where you receive alerts when incidents occur or resolve. You can combine multiple channels.

You can configure which channels receive notifications for each monitor individually. Notification suppression rules (e.g., minimum interval between consecutive alerts) are also available.

Failure Threshold (flapping suppression)

Alerts are only sent once the monitor has reached its consecutive-failure threshold (failure_threshold). The default is 2, so a single failed check followed by a successful one will not trigger an alert — the consecutive-failure counter resets to 0 on any success. This is the standard mechanism to suppress false alerts caused by transient network blips.

The threshold is configurable per monitor between 1 and 5. Set it to 1 to alert immediately on a single failure (useful for payment APIs or anything that must not stay broken even briefly). Set it to 3–5 to further suppress flapping on noisy synthetic checks.

Maximum detection latency is roughly 'check interval × failure threshold'. For example, a 1-minute interval with threshold 2 detects within at most 2 minutes; a 5-minute interval with threshold 3 detects within at most 15 minutes. For monitors under tight SLAs, lower both the interval and the threshold.

Send Test Message

Each contact has a 'Send test' button. Verify Webhook URLs, Slack channels, and SMS numbers in one click — before a real incident hits.

Multiple Contacts per Monitor

Attach more than one contact to a single monitor. Use Slack as the primary, with SMS for night-time only, for example. The Pro plan allows up to 10 Webhook contacts.

Paired Maintenance Notifications

Maintenance start and end notifications are sent as a pair. No more 'did the work finish?' confusion when only one side is delivered.

Quiet Hours

Define company-wide quiet windows (e.g. nights, weekends) when alerts are suppressed. Spans that wrap past midnight (e.g. 22:00 → 07:00) are supported. Quiet Hours target down alerts; you can opt to keep recovery and maintenance notifications on.

Notification History

Every dispatched notification (Email / Slack / Chatwork / LINE / Webhook / SMS) is logged with destination, channel, delivery status, and failure reason. Useful for verifying whether an alert actually landed and for post-mortems on overnight incidents.

Notification history is kept for 90 days, then auto-deleted. Use CSV export if you need to retain it longer.

Status Pages

Status pages let you publicly share the operational status of your services with clients. They can be customized with your branding and optionally password-protected.

Reduce "Is the site down?" inquiries from clients and build trust through transparency.

How to Create

1. Go to the "Status Pages" menu in your dashboard and create a new page
2. Select which monitors to display on the page
3. Customize the logo, colors, and custom domain
4. Share the public URL with your clients

Component Grouping

Group monitors as components like 'Frontend / API / Payments'. End users can see at a glance which area is affected.

Custom Domain

On the Pro plan you can publish at status.your-domain.com. SaaS-only feature; requires a TXT record for domain verification.

Password Protection

For limited audiences, enable password protection so only intended viewers can access the page.

Branding

Set a logo and accent color to publish under your own (or your client's) brand.

Status Page Subscriptions

End users can subscribe via email to a specific status page. Double opt-in (confirmation email) prevents typos and spam signups.

Subscribers can unsubscribe any time via the link in delivered emails. Owners can also remove subscribers from the dashboard.

What gets sent

• Incident creation and resolution
• Maintenance previews (before start) and real-time start/end notifications
• Public incident updates (progress posts)

Export Subscriber List as CSV

Export your subscriber list as CSV from the dashboard. Useful for list management or migration.

Sharing & Embedding

Public status pages can be delivered to clients in multiple ways.

Sharing methods

• One-click copy of the public URL
• Generate iframe embed code for client websites and internal portals
• QR code generation (for office monitors and event signage)

White Label / Branding

Miterl ships with the white-label features you need to deliver under your own (or your client's) brand. Logo and colors are reflected in PDF reports, status pages, and notification emails.

Standard and Pro plans can hide the 'Powered by Miterl' line entirely; the Free plan shows it as a subtle CTA link.

Logo

Upload a PNG or SVG from Account Settings → Branding. It appears on status pages, PDF reports, and notification emails.

Accent Color

Specify a HEX color and it's applied across charts, buttons, and status badges for a unified look.

Powered by Miterl

Standard and above: hide it completely from Account Settings. Free: shown as a subtle CTA link back to Miterl.

Incident Management

Miterl automatically creates incidents when a monitor detects an anomaly. You can also create incidents manually.

Automatic Detection

When a monitor detects a down state, an incident is automatically created and alerts are sent to your configured notification channels. Once recovery is confirmed, the incident is automatically closed.

Manual Creation

You can manually create incidents from the dashboard. Use this for recording unexpected issues or managing outages that monitors cannot detect. You can set the title, description, and impact scope.

Resolution Flow

Incidents have the following statuses: Investigating, Identified, Fixing, and Resolved. When you update the status, it is reflected on the status page, sharing the situation with your clients in real time.

Acknowledge (ACK)

When a member starts handling an incident, they press 'Acknowledge' to record who took ownership and when. Prevents duplicate work and 'nobody's on it' situations.

Public Updates (Progress Posts)

Updates posted to an incident also appear on the linked status page's public timeline. Choose between internal-only comments and public updates.

PDF Report Export

Export an individual incident's full timeline, response log, and root-cause notes as a PDF. Use it as a client report or post-mortem template.

Post-mortem

Capture a post-mortem for resolved incidents — summary, root cause, timeline, permanent fix, and recurrence-prevention plan. The record builds an internal knowledge base and is automatically embedded in the incident PDF for client reporting.

Search & Filters

Filter by status, period, or monitor. Useful for monthly reviews and per-client history extraction.

Maintenance Windows

Set up maintenance windows for planned downtime such as server maintenance or deployments. Monitor notifications are suppressed during the configured period, preventing false alerts.

Maintenance information also appears on status pages, allowing you to notify clients of planned downtime in advance.

• Schedule in advance by specifying start and end times
• Monitor notifications are automatically suppressed during maintenance
• Recurring schedules (weekly, monthly) are supported

Auto pause / resume around deploys

Each monitor exposes a maintenance webhook token you can hit from CI/CD. Pause the monitor at deploy start and resume it on completion — bracketing arbitrary maintenance windows without false alarms. Tokens support graceful rotation.

SLA Management

Set per-monitor SLA targets matching your client contracts. Achievement is calculated by calendar month, with allowed/remaining downtime budgets visible at a glance.

Knowing 'how much downtime budget is left this month' lets you avoid contract breaches before they happen.

Setup

1. Open the monitor edit screen and enter the contracted target (e.g. 99.90)
2. Attach an email alert contact to the monitor
3. A daily 09:00 job evaluates each monitor and notifies on danger or breach

Alert types

• Danger: triggers when remaining downtime budget drops below 25%
• Breached: triggers when achieved % falls below the target (one alert per month)

Release Watch (Focused Monitoring)

Crank up the monitoring intensity for the first few minutes to hours after a release. A short window of heightened sensitivity catches deploy-induced issues quickly.

No need to remember to turn it back off — Release Watch automatically reverts to normal at the end of the configured window and saves a screen-friendly report and history.

How it works

1. From the monitor detail page, press 'Start Release Watch'
2. Choose the duration (e.g. 30 min, 1h, 3h)
3. When the time elapses, the monitor returns to normal mode automatically
4. Review the per-run report from the history list

What's in the report

Response times, error counts, and incidents during the focused window are summarised in a screen report. Useful for asking 'did that release go cleanly?' after the fact.

Trigger from CI/CD via webhook

Each monitor exposes a release-trigger webhook token. Have GitHub Actions (or any CI) start the focused window automatically on deploy — no need to remember to click 'Start'. Triggers fired during a maintenance window are blocked automatically to avoid colliding with planned downtime.

Incident Drill

An on-call training mode that uses your real production environment. Trigger an intentional incident and verify your team's detection and response flow actually works.

Drill incidents are completely excluded from public status pages and subscriber notifications. Clients see nothing.

Important: Drills are for internal training only. They are never shown on public-facing pages — by design. The trade-off is intentional, so detection / notification / response practice can happen safely on production.

How to run a drill

1. From the monitor detail page, choose 'Start Drill'
2. Pick a duration and notification channels (hidden from public pages)
3. On-call responders detect and respond as they normally would
4. The drill auto-stops at the scheduled time and a report is generated

Drill Report

Visualises time-to-acknowledge (MTTA), time-to-recover (MTTR), and the responder. Use it to find the next improvement target.

Pre-launch Audit

Verify multiple URLs in one batch before going live — checks HTTP responses, SSL certificates, required keywords, and response times. Generates a pass/fail report or CSV for client deliverables.

Run from the dashboard, or hook into your CI/CD pipeline via the API. Failed audits return HTTP 422 so the pipeline can automatically block the deployment.

What's checked

• HTTP status (must be 2xx)
• SSL certificate validity (HTTPS only)
• Required keyword presence (optional)
• Response time (recorded in ms)

CI/CD integration via API

Create with POST /api/v1/pre-launch and poll with GET /api/v1/pre-launch/. The HTTP status code tells your pipeline whether to proceed.

# Create audit
curl -X POST https://miterl.com/api/v1/pre-launch \
  -H "Authorization: Bearer sk-xxxxx" \
  -d '{"name":"deploy-abc","urls":["https://staging.example.com"]}'
# → 202 Accepted, returns {"data":{"id":42}}

# Poll status
curl https://miterl.com/api/v1/pre-launch/42 \
  -H "Authorization: Bearer sk-xxxxx"
# → 200 if all passed / 422 if any failed / 202 if running

Full GitHub Actions / GitLab CI examples here

Investigation Service

With the Standard and Pro plans, you can request the Miterl team to investigate the root cause of incidents. We analyze server logs and network data, then deliver a report with findings and recommended actions.

Request Flow

1. Click "Request Investigation" from the incident detail page in your dashboard
2. Provide a description of the situation and any access credentials, then submit
3. The Miterl team conducts the investigation (typically 1-3 business days)
4. Investigation results and recommended actions are shared as a report

The Standard plan allows up to 1 request per month. The Pro plan allows up to 3 requests per month.

Pick from Recent Incidents

When creating a request, your recent incidents are listed as candidates. Click one to auto-fill the target incident, symptoms, and time range.

File Attachments

Attach log files, screenshots, or config snippets to your request. Better context up front means faster turnaround.

Cancel a Request

While a request is still in 'Received' status, you can cancel it from the dashboard. Useful when you submitted by mistake or the situation has changed. Once investigation has started, cancellation is no longer possible.

Client Reports

Create client groups and automatically generate monthly reports including uptime rates, response times, and incident history. Issue sharing links to deliver reports to clients, making the value of your maintenance services visible.

Report Creation Flow

1. Create a client group from the "Clients" menu and associate the relevant monitors
2. Monthly reports are automatically generated at the end of each month (manual generation is also available)
3. Issue a sharing link and send it to the client via email or chat

Reports can be customized with logos and comments to match your brand. Available on Standard plans and above.

API

A REST API for managing monitors, incidents, and pre-launch audits. Use it for CI/CD pipelines and internal tool integrations.

Issuing an API Key

Create keys from the 'API Keys' menu in the dashboard. Scope keys narrowly to limit blast radius if leaked. The full key is shown only once at issuance — make sure to save it.

# List monitors
curl https://miterl.com/api/v1/monitors \
  -H "Authorization: Bearer sk-xxxxx"

# Pause a monitor
curl -X POST https://miterl.com/api/v1/monitors/123/pause \
  -H "Authorization: Bearer sk-xxxxx"

Main endpoints

• GET/POST/PUT/DELETE /api/v1/monitors — Monitor CRUD
• POST /api/v1/monitors//pause, /resume — Pause and resume
• POST /api/v1/pre-launch — Trigger pre-launch audits
• GET /heartbeat/ — Heartbeat ping endpoint (call from cron)

All requests and responses are searchable in the API Request Log. Failed Webhook deliveries can be inspected and retried (Pro plan).

Two-Factor Authentication (2FA)

Add a second verification step using TOTP (time-based one-time passwords) via authenticator apps like Google Authenticator or 1Password.

How to enable

1. Open Account Settings → Two-Factor Authentication
2. Scan the displayed QR code with your authenticator app
3. Enter the 6-digit code from the app to enable
4. Generate recovery codes and store them somewhere safe

Recovery Codes

Single-use codes for when you lose your authenticator. Print them or save them in a password manager. Regenerate them if you start running low.

Audit Log & API Request Log

Track who did what, when, and which API calls were made. Use it as a starting point for incident response and security investigations.

Log types

• Audit Log: user actions (create / update / delete / invite / role change). Filter by action, actor, or time range.
• API Request Log: every API call. Filter by endpoint, API key, or status code.
• Both logs support CSV export.

Retention varies by plan: Free=7 days / Standard=30 days / Pro=180 days. For long-term archives, schedule periodic CSV exports.

Team Management

Invite team members and manage role-based access permissions. You can also configure notification preferences for each member individually.

Workspaces

Split a single company account into logical 'workspaces' to scope monitors and members. Carve up by client, team, or project as you need.

Member / Viewer roles can be pinned to specific workspaces, limiting which monitors they see and act on. Owner / Admin always have cross-workspace access.

Assigning members

Pick the workspaces from the member edit screen — the visible monitor scope updates immediately.

Access control

MonitorPolicy enforces workspace membership; unrelated monitors disappear from both list and detail views. Useful for keeping Client A's responder away from Client B's incidents.

Per-plan limits

Free=1 / Standard=3 / Pro=Unlimited. Free still gets one default workspace automatically, so the feature is invisible until you need it.

Plans & Pricing

Miterl offers three plans. Start with the Free plan and upgrade as your needs grow.

See the plan comparison page for detailed pricing. Annual billing includes a discount.