Maintaining monitoring,
even on quiet days.

Services keep changing, and the monitors you built will eventually stop fitting. On each patrol, AI reviews your whole monitoring setup at the interval you set, and maintains only what needs it. Everything it does is kept on record.

  • Set the patrol interval in hours
  • Database descriptions are rebuilt as the schema changes
  • "Patrol now" lets you run a review on the spot
Patrol03:00

Reviewing monitors and database descriptions.

Updated description: demo_shop
Updated monitor: Payment success
Deleted monitor: Old campaign sign-ups
Updated memory: handling of pending payments

Updated the description, 2 monitors, and 1 memory. The other monitors fit the service as it is now.

Challenges

Sound familiar?

Monitors you built have quietly drifted out of step with reality

Monitors no one uses anymore keep generating noise

There's no time to review your monitoring

What it does

Monitoring that
never goes stale.

01

Reviews monitors

Checks whether each query, collection interval, judgment interval, and description still fits the service as it is now, and fixes them if not. Missing monitors get added.

02

Retires monitors that have served their purpose

Monitors no longer needed, such as those on unused tables or finished campaigns, are deleted.

03

Rebuilds database descriptions

If the schema has changed, AI rebuilds its understanding of what system the database is and where its core lies.

04

Tidies up memory

Rewrites stale entries and deletes ones that were wrong.

Details

What AI does on patrol

It only touches what needs it. Each patrol records what was reviewed.

Update descriptions

Rereads the schema and brings the database description up to date.

Update monitors

Fixes queries, intervals, descriptions, and chart styles.

Delete monitors

Deletes monitors that have served their purpose.

Maintain memory

Rewrites and deletes entries.

How to use

Set up in 3 steps

All you need is a database connection string or an account connection. Nothing to install on your servers.

  1. STEP 1

    Choose the patrol interval

    On the Patrol page, set how many hours apart patrols run.

  2. STEP 2

    AI reviews

    At the interval you set, AI reviews your whole monitoring setup.

  3. STEP 3

    Check the record

    What was reviewed and what was changed is kept on the Patrol page.

Who it's for

Who it's for

  • Your service changes often
  • Monitors have multiplied and maintenance can't keep up
  • You're bothered by alerts from outdated monitors
  • You want to review your monitoring regularly
  • You want a record of what AI changed
Use cases

Use cases

Schema changes

Bring new tables into monitoring

When a new feature adds tables, the patrol rebuilds the database description and reworks monitors as needed.

Campaign ended

Retire monitors no longer in use

Monitors that have served their purpose, like sign-ups for a finished campaign, are deleted by AI.

Leave monitoring maintenance
to AI, too.

The patrol interval can be set per project, and every change is kept on record.