How it works

Curade Mini does not monitor anything itself. It reads each environment from your organisation's monitoring platform as you look, adds its own analysis on top, and keeps the few things that are yours, such as your widgets, your chats and your alerts.

Where the data comes from

Each environment connects to your organisation's monitoring platform through an access token Core Consulting sets up for it. When you open a page, the app reads what it needs through that connection: the problems, the applications, services and hosts, their metrics and the events recorded on them. Nothing is copied ahead of time, so a page always shows what monitoring holds at the moment you look.

The connection only reads. Nothing that reads it, CLEO and Cluemetry included, changes anything in your monitoring platform.

What it works out

Some of what you see is Curade Mini's own work rather than a figure your monitoring platform publishes:

• CLEO's answers, which draw on the same monitoring data and on how the app works (CLEO);
• the health score of each environment (Health score);
• the grade of a service, worked out from its response time and failure rate over your time window;
• the short reason on a list card that needs attention, and the line above a list when several items share a cause;
• every explanation behind a Why?, which Cluemetry works out from monitoring's own facts (Cluemetry).

What runs on a schedule

These run on Core Consulting's side on their own schedule, whether or not anyone has Curade Mini open:

• your monitoring alerts, checked every few minutes and never on your phone, which is why an alert reaches you as a push notification with the app closed (Monitoring alerts);
• the notices the service writes itself, such as a warning that an environment's access token is about to lapse, which arrive the same way.

Who sees what

• Your role decides which pages you open, and your environments decide whose data you see (Roles and permissions).
• A dashboard is private to you, and nobody else sees its widgets (Dashboard).
• A chat with CLEO starts Private, so only you see it until you share it. The admins of your environments, and Core Consulting staff who run the service, can still read it (CLEO).
• CLEO writes its answers with the AI provider chosen for the environment, and asks you before your first message goes to that provider (CLEO).
• Your monitoring alerts are yours alone too, and nobody sets them for you.