The activity log is Uptimia's audit trail. It writes one entry every time someone in your account changes a monitor, a maintenance window, an alerting team, a template, an integration or a branding theme, handles an incident, changes who has access, or signs in, naming the person and the exact time. It answers "who deleted this monitor?", "who paused it?" and "who signed in from where?", and it is what a security questionnaire is asking about. For individual check results, see Monitoring Logs.
Before You Start #
- The activity log is visible to the account Owner and to Admin members only. Editor, Read-only and Accounting / Billing seats cannot open it.
- It is available on every plan.
Where the Activity Log Is #
Go to People → Audit Log in the sidebar. Its heading reads Audit log, with the line "Who changed what, and when. Kept for 12 months (sign-ins and their IP addresses for 90 days); times in your account timezone."
The sidebar entry does not appear for members without the right role. If one of them opens /cp/activity directly, Uptimia sends them to their own home page: the dashboard for Editor and Read-only seats, the subscription page for an Accounting / Billing seat.
What Gets Recorded #
| Object | Recorded when |
|---|---|
| Monitors (every monitor family) | A monitor is created (including a duplicate of an uptime monitor, named COPY <original name>), edited with the list of changed settings, deleted, paused or resumed, put into or taken out of maintenance, or one of its incidents is deleted |
| Incidents | Someone acknowledges an incident or clears the acknowledgement, escalation resumes after an acknowledgement, someone opens or resolves a manual incident, or someone changes an incident's availability impact |
| Security findings | Someone marks a finding on a Security monitor as expected, or undoes that |
| Maintenance windows | A window is scheduled, updated or deleted |
| Teams and Templates | An alerting team or a monitor template is created, edited or deleted |
| Groups | Monitors are added to or removed from a group in one step, for example "Added 52 monitors to uptime-only" |
| Integrations and branding themes | One is created, edited or deleted (a theme can also be duplicated) |
| Account time zone | Someone changes it, with the old and new zone |
| Team members and API keys | A member is invited, the invite is re-sent or revoked, a member is removed, their role or monitor access changes, or an API key is created or deleted |
| Sign-ins and two-factor | The owner or a member signs in, or a sign-in attempt against their email fails (wrong password, wrong or reused code, lockout), with the IP address, location and browser. Two-factor changes are recorded too: an authenticator app or email codes turned on or removed, new recovery codes, a recovery code used, and an Owner or Admin resetting a member's two-factor sign-in |
Attempts with an email address that has no Uptimia account are not recorded, because there is no person to file them under.
Not recorded in the activity log: contacts, escalation policies, status pages, scheduled reports, location profiles, and creating, renaming or deleting monitor groups.
Most automatic events are absent too. A maintenance window opening and closing on its own schedule writes nothing, and neither does a monitor going down, a check failing or an alert being sent. The activity log records what a person did; incidents record what happened to your services. The exception is escalation resuming after an acknowledgement, which is shown with a System actor.
Reading an Entry #
The feed is grouped by day, newest first, in your account's time zone. Each day carries a heading like Monday, Aug 18 · Today.
A row reads left to right: the time in 24-hour form, the actor's avatar, then the sentence. An edit reads Jane Cooper edited Uptime monitor Checkout API. The line under it says Changed: Name, Check interval. A sign-in row shows the location, the IP address and the browser under the sentence, and a failed sign-in is shown in red.
The verbs match the action: created, edited, deleted, paused, resumed, scheduled maintenance window, updated maintenance window, deleted maintenance window, put into maintenance, took out of maintenance, acknowledged, opened a manual incident, marked as expected, invited, signed in. Non-monitor objects read as "created team" or "deleted template", never "created Team monitor".
The actor is the account owner or a team member. If that person has since been removed from the account, their older rows read Removed member, and the entries stay in the log. An acknowledgement made from an alert link without signing in shows a link icon as the actor, because nobody was signed in.
Above the feed, one line sums up the selected date range, member and search: how many events, how many people made them, and how many deletions. Click the deletions count to open the Deletions tab.
Filtering the Log #
Tabs sit above the feed, and the other filters sit beside them:
| Control | What it does |
|---|---|
| Tabs | Everything; Changes (creates, edits, pauses and resumes, maintenance, availability impact changes and Mark as expected); Deletions; Incidents (acknowledgements and manual incidents); Access (team members and API keys); Sign-in & 2FA (sign-ins, failed attempts and two-factor changes) |
| Search | Matches the object name, the action, the type and the entry's stored details |
| Member dropdown | Anyone, one person, Alert recipients (links) or System |
| Date range picker (beside Export CSV) | Today, Yesterday, Last 7 Days, Last 30 Days, This Month, Last Month, or a custom range |
The feed shows 25 entries per page, and changing any filter returns you to page 1. The tab is kept in the address, so /cp/activity?tab=access opens the Access tab directly.
Opening an Entry for the Full Detail #
Click any row to open the detail panel on the right. It carries:
- A status badge naming the action: Monitor created, Monitor edited, Monitor deleted, Monitor paused, Monitor resumed, Maintenance scheduled, Maintenance ended, Incident acknowledged, Manual incident opened, Availability impact changed, Signed in, Failed sign-in and so on. Other objects get their own wording, for example Integration created.
- The item's name, its type and its number, for example "Uptime monitor · #4182".
- The time to the second, the day, and how long ago it was.
- Performed by, with the person's email, their role, and "(account owner)" where it applies.
- On a sign-in, From: the IP address and location. The Details list adds the browser, the device and the full user agent, and for a failed attempt Why it failed.
- Source (where it applies, for example the alert link or the API for an acknowledgement), Action (Uptimia's own internal name for what happened), Object, When, and Record, which shows the entry's own number after a #.
- Changed fields on an edit: one chip per changed setting. Each chip uses the monitor editor's own name for the setting (Name, URL, Check interval, Timeout, Locations, Escalation policy and so on). When a save changed only which contacts, groups or steps the monitor uses, the panel says "No monitor settings changed — the edit touched only contacts, groups, or steps."
- Related activity on this object: up to five other entries for the same monitor from the current page.
For a monitor entry, two buttons sit at the top of the panel. The first is Open monitor; the second is a filter shortcut that narrows the feed to that one person's activity ("Only Alex's activity"). An acknowledgement entry has Open incident instead of Open monitor. Other entries show the filter shortcut only.
Entries for Monitors That No Longer Exist #
The log stores the monitor's name at the moment it writes the entry, and it does not point back to the monitor itself. Deleting a monitor never erases its history. The deletion row keeps a readable name and carries a small deleted marker in the feed. Every earlier entry for that monitor stays in the log too.
The detail panel for any of those entries disables Open monitor. The line "This monitor no longer exists." appears beside it, and the Object fact reads "no longer exists — name kept from the log".
Exporting the Log to CSV #
Click Export CSV at the top right of the page. The export honors every filter currently applied (tab, member, date range and search) and returns up to 10,000 rows, newest first. The file is named uptimia-audit-log-YYYYMMDD.csv and has thirteen columns:
Record #, When (with your account's time zone in the header), Member, Email, Role, Source, Action, Type, Monitor, Monitor ID, Details, IP, Location
IP and Location are filled on sign-in rows. If more than 10,000 rows match, the file holds the newest 10,000 and its last line says it was cut. Narrow the date range and export in slices.
How Long Entries Are Kept #
Activity entries are kept for 12 months. Sign-in entries, which carry IP addresses, are kept for 90 days. Uptimia removes older rows nightly, and the page states both windows under its heading. There is no setting to extend or shorten it, and no way to delete an individual entry. Export anything you need to keep past 12 months. Monitoring data has its own, plan-dependent windows: see Data and Log Retention.
Activity Log vs Monitoring Logs vs Incidents #
The names are close enough that people open the wrong one.
| Page | Where | Answers | Kept for |
|---|---|---|---|
| Audit Log | People → Audit Log | Who changed the configuration, and when | 12 months (sign-ins 90 days) |
| Monitoring Logs | Logs | What each individual check returned, per probe | Your plan's retention window |
| Incidents | Incidents → Active | Which monitors went down, for how long, and who acknowledged | Your plan's retention window |
If a monitor stopped alerting, one of the three has your answer. The Audit Log names whoever paused or edited it. Monitoring Logs shows whether the checks have been passing all along, and Incidents shows an incident that opened and closed while nobody was watching.
Team Access Changes: Invites, Role Changes and Scopes #
Changes to who has access also have their own summary, the Recent access changes card on People → Users. It shows the latest 20 events, written as "{person} {what they did}":
| Event | Written when |
|---|---|
| Invited | A team member is invited, naming the role and any monitor-group limit |
| Role changed | A member moves between roles, naming both |
| Scope changed | A member is limited to monitor groups, or given access to all monitors |
| Removed | An activated member is removed |
| Invite revoked | A pending invite is canceled |
| Invite resent | An activation email is sent again |
| 2FA reset | An Owner or Admin turns off a member's two-factor authentication |
The card is visible to the Owner and to Admins, keeps the same 12 months of history and has no export. Invites, role and scope changes and removals, plus API keys, also appear in the audit log's Access tab, which can be exported. A 2FA reset appears in its Sign-in & 2FA tab. For what each role can do, see User Roles and Permissions. The invite lifecycle is in Inviting Team Members.