02 · Anticipate

Atlassian Preventive Service.

We detect deviations before they turn into incidents and keep the Atlassian ecosystem stable, tidy and predictable.

Principles

Operational discipline and recurrence

It's not monitoring for its own sake. Every preventive action has a purpose, a cadence and a trace.

We act before the issue becomes visible to the user.

Usage trends, contracted limits and effective consumption.

Each preventive is logged in JSM with its time spent and outcome.

Control areas

Five areas that cover the health of the Atlassian ecosystem, each with concrete preventive actions inside a living catalog.

01
Limits and usage · Monthly
Contracted vs. consumed licenses, storage, automations and Rovo. When consumption nears 80%, we open a preventive ticket and propose actions.
02
Availability · Continuous
Atlassian status monitoring with automatic alerts. If the client's tenant is affected, we open an incident and trigger proactive communication.
03
Security · Monthly
Users, roles and permissions. Review of API tokens, external users and authorized domains. Data classification every quarter.
04
Configuration and governance
Atlassian release tracks, cross-product links and audit log review to detect anomalous behavior.
05
Backups
Daily backup with monitoring and monthly restore drill in sandbox when the client has that capability.

Operations

No invisible work. Every preventive action lives as a controlled ticket in JSM.

Dedicated ticket type with a catalog of preventive services modeled in Assets, in two levels: area and concrete action.

Tasks are generated based on the defined cadence, using a dedicated service account.

Each type has an estimated duration. We compare estimated vs. actual to improve planning.

When a preventive surfaces a structural improvement, it moves to the Evolutionary Service with its own prioritization.

Continue the journey →