Alle Artikel

Getting Started

Was ist CICDoo Erste Schritte: der Onboarding-Assistent Das Dashboard und die Infrastrukturkarte

Concepts

Produktions-, Staging- und Development-Stages Domains, Subdomains und SSL Odoo-Versionen und -Editionen (Community vs. Enterprise) Workspaces und Teamzusammenarbeit

Servers

Einen Server hinzufügen Server-Domains und DNS Einen Load Balancer verwenden Server-Aktionen: Deploy, Logs und Diagramme Deleting a server

Projects & Git

Ein Projekt erstellen GitHub verbinden Project GitHub settings and webhook GitLab verbinden Branches und Instanzen Projekte mit Tags versehen und filtern Hochverfügbarkeit mit App-Knoten Project environments, extensions and deletion

Instances & Console

Eine Instanz erstellen Eine Instanz neu starten, stoppen und entfernen Branches zwischen Stages mergen Web-IDE und Fernzugriff SSH access to instances Instanzeinstellungen erklärt Deployments und die Job-Warteschlange

Agent Tasks

Was Agent-Aufgaben sind Agent-Aufgaben einrichten Eine Aufgabe ausführen und das Ergebnis prüfen Agent-Zeit und Aufstockungen Agent insights and task filters

Monitoring & Backups

Deine Instanz überwachen Backups und Wiederherstellung S3 storage, uploads and bulk backup actions Warnbenachrichtigungen (E-Mail und SMS)

Workspaces & Permissions

Workspace-Mitglieder einladen Mitgliederberechtigungen und Ressourcenzugriff Ein Mitglied kann eine Ressource nicht sehen oder nutzen Audit log and server activity

Account & Security

Zwei-Faktor-Authentifizierung (2FA) Profil- und Integrationseinstellungen Passwörter und Kontowiederherstellung

Billing & Plans

Tarife und Preise Dein Abonnement upgraden und verwalten Wenn ein Projekt-Abonnement unbezahlt bleibt Das Channel-Partner-Programm Onboarding a client as a partner

Support & Tickets

Ein Support-Ticket eröffnen Hilfe vom CICDoo-Team erhalten

Troubleshooting

Fehlerbehebung: Server kann nicht verbunden werden Fehlerbehebung: ein Deployment ist fehlgeschlagen Fehlerbehebung: git push schlägt mit 403 fehl nach Verschieben eines Repositorys Fehlerbehebung: meine Instanz ist ausgefallen oder langsam Fehlerbehebung: Domain- oder SSL-Probleme

Workspaces & Berechtigungen

Audit log and server activity

How to use the Audit Log page to see who did what on your servers, projects and instances, filter it, read each entry, and open the activity feed for a single server.

What the audit log records

The Audit Log page shows who did what on your servers, projects and instances. Every change made through the app is recorded, such as deploying a server, restarting an instance, changing settings, inviting a member or creating a backup. Each entry records whether the action succeeded, failed, or was denied because the person lacked permission.

The log covers the whole workspace. Dates are in UTC, and entries are kept for 90 days.

Who can see it

  • The workspace owner and admins always see the Audit Log.
  • Other members see it only if they have View the audit log switched on in their permissions. See Member permissions and resource access.
  • If you work on your own account without a workspace, you see the log for your own account.

Without the permission, Audit Log does not appear in the menu, and the Activity item is hidden from the server actions menu.

Open the audit log

  1. Click Audit Log in the left menu.
  2. The newest entries are at the top. Use the page controls at the bottom to see older entries.

Each row shows:

  • When: how long ago the action happened. Hover over it to see the exact date and time in UTC.
  • Who: the person's name and email address.
  • Action: what was done.
  • On: the server, project and instance involved. Project and instance names are links when the item still exists.
  • Outcome: Success, Failed or Denied.
  • IP address: the address the request came from, partly masked. Click it to copy the full address.

See the details of an entry

  1. Find the entry in the list.
  2. Click the arrow at the end of the row (shown only when the entry has more detail).
  3. The row expands to show the details of the change and the browser that made the request.
  4. Click the arrow again to collapse it.

Filter the audit log

  1. Click Filters above the list.
  2. In the Filter audit log window, set any of these:
    • Who: one person, or Everyone.
    • Server, Project and Instance: type to search, or leave on All servers, All projects or All instances.
    • Category: the area of the platform, such as Members, Project, Instance, Server, Backup, Git, Billing or Support.
    • Outcome: Success, Failed or Denied, or All outcomes.
    • From and To: a date range, in UTC.
  3. Click Apply. Reset clears the window, and Cancel closes it without changing anything.

The applied filters appear as chips under the Filters button, and the button shows how many are active. Click the cross on a chip to remove that filter, or Clear all to remove them all. Filters stay in the page address, so you can bookmark or share a filtered view with someone who can see the log.

See activity for one server

  1. Go to the Servers page.
  2. Open the Actions menu for the server and click Activity.
  3. The Server activity window lists who did what on that server and the instances it runs, newest first. Each line shows the action, the person, the time and, where relevant, the instance and the masked IP address. Failed and denied actions are marked with a badge.
  4. Click the arrow on a line to see its details.
  5. Click Load more to see older entries, or Refresh to fetch new ones.
  6. Click Open in audit log to see the same entries on the full Audit Log page, where you can filter them further.

Tips

Related: Member permissions and resource access, Workspaces and team collaboration, Server actions: deploy, logs and charts.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Zurück Ein Mitglied kann eine Ressource nicht sehen oder nutzen

Kommst du nicht weiter? Erstelle ein Ticket in der App oder sprich mit einem Techniker.