Skip to content
User guide

Activity, alerts and audit

Everything that happened in your organisation with its reason, the alerts that fired, every API request and the errors behind them, telemetry, and the audit's integrity and reports.

Activity answers "what happened, who did it, and why". Its tabs:

Tab

What it shows

Feed

Every deploy, job run, sign-in and change, each with its reason. Filter by person, team, kind and period (Last 24 hours to Any time) and by result (Done, Failed, Refused). Views include By team, By hand (people's own actions), Scheduled, Releases, Notes and the Chronicle

Alerts

Alerts from your rules, uptime checks and jobs, with a count of the ones firing. Acknowledge or Resolve each, with an optional note for the team. Views for rules, silences, channels and uptime checks

Requests

"Every call to the API that the audit recorded": search by path, person or reference, Failed only. Open one to see what happened on that request: its audit entries in order and the work it started

Errors

Failed requests (the server could not do it), Refused requests (not allowed for that person), the different error codes with what each means

Telemetry

How your apps are used and how fast they answer

Integrity

The audit trail is a hash chain: this checks that no entry was changed or removed (team admins and up)

Reports

Audit report definitions and their runs; export them

Complete audit

For auditors only

Set up alerts

  1. Activity > Alerts, open the rules view and click New rule: pick what to watch (a project, a job, an uptime check), the condition and the severity.

  2. Open the channels view and add where alerts go: in-app (the bell and Home's Needs attention), e-mail through your organisation's mail sender, or a webhook (the address is kept in the Vault). Chat and paging tools are add-ons. Send test checks a channel.

  3. New silence quiets a rule for a while, for example during maintenance.

Projects can override thresholds under Project > Settings > Domains and health > Alerts.

Error references

When something fails, the console shows a short reference. Paste it into Activity > Requests to see exactly what happened on that request, or quote it to support@remplatforms.com; it lets support find your request without asking for screenshots.

Notifications

The bell at the top collects your notifications (alerts, approvals, invitations, expiring tokens). Open one, mark it read or unread, or archive it; nothing is deleted. Settings > Notifications decides what also reaches your inbox (E-mail right away or a Daily summary at a Summary time).

Download: PDF · Word · Markdown