Tous les articles

Getting Started

Qu'est-ce que CICDoo Pour commencer : l'assistant d'intégration Le Tableau de bord et la Carte d'infrastructure

Concepts

Étapes de production, staging et développement Domaines, sous-domaines et SSL Versions et éditions d'Odoo (Community vs Enterprise) Espaces de travail et collaboration en équipe

Servers

Ajouter un serveur Domaines de serveur et DNS Utiliser un répartiteur de charge Actions de serveur : déploiement, journaux et graphiques Deleting a server

Projects & Git

Créer un projet Connecter GitHub Project GitHub settings and webhook Connecter GitLab Branches et instances Étiqueter et filtrer les projets Haute disponibilité avec des nœuds applicatifs Project environments, extensions and deletion

Instances & Console

Créer une instance Redémarrer, arrêter et supprimer une instance Fusionner des branches entre étapes Web IDE et accès distant SSH access to instances Les paramètres d'instance expliqués Déploiements et file d'attente des tâches

Agent Tasks

Ce que sont les tâches de l'agent Configurer les tâches de l'agent Exécuter une tâche et examiner le résultat Temps d'agent et recharges Agent insights and task filters

Monitoring & Backups

Surveiller votre instance Sauvegardes et restauration S3 storage, uploads and bulk backup actions Notifications d'alerte (e-mail et SMS)

Workspaces & Permissions

Inviter des membres dans un espace de travail Permissions des membres et accès aux ressources Un membre ne peut pas voir ou utiliser une ressource Audit log and server activity

Account & Security

Authentification à deux facteurs (2FA) Paramètres de profil et intégrations Mots de passe et récupération de compte

Billing & Plans

Forfaits et tarifs Mise à niveau et gestion de votre abonnement Si un abonnement de projet reste impayé Le programme de partenaires de distribution Onboarding a client as a partner

Support & Tickets

Ouvrir un ticket de support Obtenir de l'aide de l'équipe CICDoo

Troubleshooting

Dépannage : impossible de connecter un serveur Dépannage : un déploiement a échoué Dépannage : git push échoue avec une erreur 403 après le déplacement d'un dépôt Dépannage : mon instance est hors service ou lente Dépannage : problèmes de domaine ou de SSL

Espaces de travail et permissions

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.

Précédent Un membre ne peut pas voir ou utiliser une ressource

Toujours bloqué ? Ouvrez un ticket depuis l'app ou parlez à un ingénieur.