APEX Project Eye 26.2 introduces SLA in Watchtower, letting teams define recurring compliance activities, sign them off in seconds, and prove, with a full history, that someone was really watching.

Enabling SLA in APE 26.2

To start using SLA, first enable it for your APE environment. In Administration, open Configuration Options and turn on Feature: SLA to make Service Level Agreements (SLA) available throughout Watchtower.

Finding SLA in Watchtower

Once enabled, Watchtower's landing page gains a new Service Level Agreements (SLA) entry alongside Dashboard, Sensors, Scans, Escalations, and Administration. This is where day-to-day sign-offs happen, while activity types are defined under Administration.

APE’s Watchtower Landing Page.

Defining SLA Activity Types

From Watchtower → Watchtower Administration → SLA Activity Types, define reusable activity types describing what needs to be reviewed and how often.

Each activity type has a frequency (hourly, daily, weekly, or monthly, with day-of-week control), a plain-language agreement or condition describing what "done" means, a start date and optional end date, a Required flag, and a retention period that determines how long its sign-off history is kept. APE 26.2 ships with a default activity, APE Watchtower Review, checked weekly, so there's a working example in place before you define your own.

Default weekly activity, APE Watchtower Review, is pre-configured, but you can add your own.

Signing off, quick or guided

On the Service Level Agreements (SLA) page, the SLA Activities table lists every active activity with its frequency, last-checked date, and current status. For the routine case, click the checkmark icon to quickly sign off directly from the list — no need to open anything else.

Quick Sign-off option under the SLA Activities region requires only one click.

For a closer look before confirming, use New Sign Off to open the guided SLA Sign-Off modal. It lists every due activity with its frequency, due date, and agreement conditions, and lets you add a comment per activity plus an overall comment before confirming. Each activity can be signed off once per day; multiple activities can be signed off independently of one another.

If you want to add a comment per activity and/or an overall comment, use the SLA Sign-off modal.

Missed checks, retroactive fill-in, and retention

If a required activity's period passes with no sign-off, APE computes the expected check date automatically, marks it Overdue, and —once the period closes — logs it as a missed check in the SLA Sign-Off History table. Users with the appropriate access can fill in a missed date retroactively straight from the SLA Sign-Off History region.

Admins can fill missing checks retroactively under the SLA Sign-Off History region

The Sign-Off History report is interactive and exportable to CSV or PDF, and every entry can be drilled into for the full SLA Check Detail: who signed off, when, their comments, and how the result compares to the activity's agreement. History is purged automatically once it passes each activity's configured retention window, using the same purge job that already manages the rest of APE's data.