All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Server Monitoring
Start now
More

Features

Industries

Reference

More

Server Monitoring · Available now

See service health and follow each response.

Server Monitoring keeps service availability checks and server resource samples beside the assets and services they describe. Operators can compare a failed check with CPU, memory and free disk observations, then open an incident against the affected service and asset.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewChanges In Review
Server Monitoring · Changes

Changes In Review

Changes in one list

New change
Changes in view
6
Low
2
Medium
2
High
2
IdSummaryRiskScheduled startScheduled endStatus
INC-2026-0412Queue lag exceeded five minutesLow12 Oct19 OctReview
CHG-2026-0184Replica storage nearing capacityMedium04 Nov06 NovReview
AST-REN-001Sign-in failures from west regionHigh02 Nov11 NovReview
RBK-OPS-023Gateway certificate due for renewalLow18 Oct24 OctReview
OUT-2026-0061Attachment uploads timed outMedium18 Oct22 OctReview
6 of 6 records
INC-2026-0412Changes · CHN-40181
Low
SummaryQueue lag exceeded five minutes
Scheduled start12 Oct
Scheduled end19 Oct
StatusReview
ServiceInventory database
Review changeCHN-40181 · INC-2026-0412

The Change Reviewer approves or rejects the change and records a reason.

Waiting for Change Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
53
Saved views
16
Roles with set permissions
6
Reports and dashboards
10
Features

See the current service picture

Every feature works on the same records. Pick one to see the screen your team works in.

Service health

Review availability checks and server resource samples against the service and asset they describe.

  • Service context
  • Check history
  • Asset samples
  • Services
  • Assets
  • Availability checks
  • Server samples
  • Maintenance windows
  • Integration receipts
Explore service health
OverviewFailed Availability Checks
Server Monitoring · Service health

Failed Availability Checks

Availability checks

New
IdChecked atSuccessLatency MSProbe locationService
INC-2026-041230 OctNo810Portland, OregonBilling scheduler
CHG-2026-018404 NovNo330Reno, NevadaNotification delivery
AST-REN-00127 OctNo100Boise, IdahoInventory database
RBK-OPS-02319 OctNo620Tacoma, WashingtonBilling scheduler
OUT-2026-006117 OctNo730Denver, ColoradoInventory database
6 of 6 records
INC-2026-0412Availability checks · AC-99028
No
Checked at30 Oct
Latency MS810
Probe locationPortland, Oregon
ServiceBilling scheduler
Example screen with sample data
Process

From observation to recovery

Monitor and respond ships ready to use. One step needs a named approval before the work moves on: Review change (Change Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Observe service

    Review a check and nearby resource samples for the affected service.

    INC-2026-0412CHN-40181 · Monitoring Operator
    Observe serviceBy Monitoring Operator

  2. Open incident

    Create an owned incident with priority, service and asset.

    INC-2026-0412CHN-40181 · Monitoring Operator
    Open incidentBy Monitoring Operator

  3. Acknowledge

    The assigned responder accepts the case and records a response event.

    INC-2026-0412CHN-40181 · Incident Responder
    AcknowledgeBy Incident Responder

  4. Investigate

    Keep attributed updates and the service effect beside the incident.

    INC-2026-0412CHN-40181 · Incident Responder
    InvestigateBy Incident Responder

  5. Review change

    The Change Reviewer records the decision and reason before implementation.

    INC-2026-0412CHN-40181 · Change Reviewer
    Review changeBy Change Reviewer
    ApprovalThe Change Reviewer approves or rejects the change and records a reason.

  6. Verify recovery

    Review a later successful check, record restoration and resolve the incident after owner review.

    INC-2026-0412CHN-40181 · Monitoring Operator
    Verify recoveryBy Monitoring Operator

Start with Incident response

Inside a record

Connect the sources your team trusts

Open any change to see its change reviews, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Summary, Scheduled start, Scheduled end and Status.

  2. 2
    Change reviews

    Each line is linked to this change.

  3. 3
    Who works on it

    Change Reviewer, Release Operator and Admin, each with their own permissions.

  4. 4
    Process stages

    Review change and Implement change, with the role that acts.

  5. 5
    Approvals

    Review change, with who decides.

Changes In ReviewINC-2026-0412
Server Monitoring · Changes

INC-2026-0412

Queue lag exceeded five minutes · Low

Log activity
1
Record details
SummaryQueue lag exceeded five minutes
Scheduled start12 Oct
Scheduled end19 Oct
StatusReview
2
Change reviews

INC-2026-0412

IdMeeting dateDecision
INC-2026-041218 OctPending
CHG-2026-018411 OctPending
AST-REN-00131 OctPending
Change reviews
6
3

Who works on it

  • Change ReviewerManage change reviews
  • Release OperatorManage Changes, Deployments, rollback checks
  • AdminManage People, Users, Services, Assets, Runbooks
4

Process stages

  • Review changeChange Reviewer
  • Implement changeRelease Operator
5

Approvals

  • Review changeChange Reviewer
    Approved
Example screen with sample data
Approvals

Put a reviewer behind each change

Change Reviewers record the decision and reason before a Release Operator implements a change.

OverviewApprovals
Server Monitoring · Overview

Approvals

Signed in as Change Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • CHN-40181INC-2026-0412
    Queue lag exceeded five minutesRequested by Monitoring Operator
    Low3dActions
  • CHN-45077CHG-2026-0184
    Replica storage nearing capacityRequested by Monitoring Operator
    Medium1dActions
  • CHN-86637AST-REN-001
    Sign-in failures from west regionRequested by Monitoring Operator
    High3dActions
  • CHN-98062RBK-OPS-023
    Gateway certificate due for renewalRequested by Monitoring Operator
    Low5dActions

Who approves what

DecisionApprover
Review changeThe Change Reviewer records the decision and reason before implementation.Change Reviewer
1 approval rule · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens Server Monitoring to the work that is theirs. Pick a role to see what it starts with.

Monitoring Operator

Reviews checks and samples and starts an incident when a service needs attention.

This is the first screen this role sees.

OverviewOpen Incidents

Open Incidents

Incidents · Monitoring Operator

Low2
INC-2026-0412Queue lag exceeded five minutes
OUT-2026-0061Attachment uploads timed out
Add
Medium2
CHG-2026-0184Replica storage nearing capacity
CHK-2026-0918Billing schedule missed overnight
Add
High1
AST-REN-001Sign-in failures from west region
Add
Critical1
RBK-OPS-023Gateway certificate due for renewal
Add
Example screen with sample data

Roles and permissions

Reports

Read health and response over time

Review service availability, resource observations, response timing and change outcomes.

Overview
Server Monitoring · Overview

Server Monitoring dashboard

This quarter

Service requests in view
6
Submitted
2
Approved
2
In progress
2

Changes by status

How far records got this quarter

StageReachedStep
Draft29
Review517%
Approved120%
Implementing1100%

Number of changes by status

Sample counts per stage

100
10Draft
10Review
10Approved
-30Implementing
-10Verified
Example screen with sample data
  1. 01Availability by service

    Count successful and failed availability checks by Service and checked at.

  2. 02Resource observations by asset

    Compare CPU percent, memory percent and disk free bytes from server samples by Asset and sampled at.

  3. 03Incident state and priority

    Group Incidents by Service, Status and Priority.

  4. 04Response timing

    Compare opened at, acknowledged at and resolved at for Incidents.

  5. 05Outage duration

    Compare started at and restored at on service outages by site code and Incident.

  6. 06Impact by incident

    Group service impacts by Incident, monitored service and service impact.

  7. 07On-call coverage

    List on call shifts by Service, Responder, starts at and ends at.

  8. 08Change review outcomes

    Group change reviews by Change, Decision and Reviewer.

  9. 09Deployment outcomes

    Compare Deployments by Service, Environment, Status and deployed at.

All reports and dashboards

Who it's for

Fit the service model to your operation

See how Server Monitoring fits your kind of team.

Internal IT operations

Give internal service owners and responders one place to follow service health and incidents.

SaaS operations

Relate service checks, deployment outcomes and customer impact during a release.

Multi-site services

Distinguish a site-specific interruption from a wider service problem.

Controls

Keep decisions and evidence together

Each stage of monitor and respond names the role that acts and the status it records, so a change is never anonymous.

OverviewMonitor and respond
Server Monitoring · Process

Monitor and respond

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
5
Tables touched
13
Acknowledge
Incident Responder
StatusOpen → Acknowledged
RecordsResponse events, Incidents
Investigate
Incident Responder
StatusAcknowledged → Investigating
RecordsIncident updates, Incidents
Review changeApproval
Change Reviewer
StatusReview → Approved
RecordsChange reviews, Changes
Monitor and respond
  1. Start
    AcknowledgeOpen → Acknowledged
    Response events
  2. Step
    InvestigateAcknowledged → Investigating
    Incident updates
  3. Approval
    Review changeReview → Approved
    Change reviews
  4. Step
    Implement changeApproved → Implementing
    Deployments
  5. Step
    Verify recoveryImplementing → Verified
    Availability checks
Example screen with sample data

See each stage in detail

AI agent

Ask Proto for the working context

Give your team an assistant for service checks, incident context and change preparation.

It can

  • Monitoring Operator: Show failed checks for a service and the nearby server samples.
  • Incident Responder: Summarize the current incident chronology and identify the assigned person.
  • Service Owner: Compare an outage record with the service impact and latest recovery observation.
  • Change Reviewer: Present the proposed window, risk, rollback plan and prior review reason.

Stays with a person

  • The people responsible for the service decide priority, impact, change approval and whether recovery is complete.
  • Ask Proto to assemble the record and show where the evidence came from.
  • The named reviewer records an approval decision, and the owner reviews the final outcome.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Server Monitoring
  • Availability probes
  • Server telemetry
  • Log sources
  • Deployment systems
  • Event intake
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 53 tables
53tables
  • Service health6
  • Incident response6
  • Outages and impact5
  • On-call operations6
  • Changes and deployments7
  • Assets and runbooks7
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Name the service

    Choose the first monitored service, owner, criticality and linked assets.

  2. Map observation sources

    Agree the check locations, sample source and event identifier convention.

  3. Set response ownership

    Add responders, shifts, escalation levels and incident priorities.

  4. Rehearse an interruption

    Record a failed check, incident, acknowledgment, impact, outage and recovery check.

  5. Rehearse a change

    Draft a change, record a human review decision, then capture the release and post-change observation.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Server Monitoring.

All questions
How do I get started?

Click Get started, then use Proto to configure Server Monitoring for your business. Begin with one service, its linked assets, an owner and a responder. Rehearse a failed check through acknowledgment and recovery before adding further coverage.

What does a failed availability check show?

It records a time, success result, latency, probe location and service. Compare the result with other checks and server samples before deciding how broadly the service is affected.

How do server samples relate to incidents?

A sample belongs to an asset and records CPU, memory and free disk observations. An incident can name the affected asset and service so the responder can compare those readings with the investigation.

Who receives an incident?

The incident has an assigned person. An on-call shift shows the planned responder for a service and time window. The team should confirm the actual handoff with acknowledgment and response events.

How is an outage recorded?

The responder records a site, outage reference, start and restoration time against an incident. The service owner can add a separate impact classification for the affected service.

Who approves a change?

A Change Reviewer records the decision and reason in the change review. The Release Operator uses that decision before implementation and records the deployment outcome.

What happens after a deployment?

Review the deployment state, rollback checkpoints and a new availability check for the service. Resolve any related incident only after the team confirms the observed result.

Can the team keep response procedures here?

Runbooks have an owner, linked service, publication state and procedure body. Responders can use published runbooks during investigation and leave feedback afterward.

How are incoming events traced?

Integration receipts retain the provider, external event identifier, receipt time, payload hash and disposition. Review rejected or failed receipts apart from the incident queue.

Set up Server Monitoring your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appServer Monitoring

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.