Todos los artículos

Getting Started

Qué es CICDoo Primeros pasos: el asistente de incorporación El Panel y el Mapa de Infraestructura

Concepts

Etapas de producción, staging y desarrollo Dominios, subdominios y SSL Versiones y ediciones de Odoo (Community vs Enterprise) Espacios de trabajo y colaboración en equipo

Servers

Añadir un servidor Dominios de servidor y DNS Usar un balanceador de carga Acciones de servidor: desplegar, registros y gráficos Deleting a server

Projects & Git

Crear un proyecto Conectar GitHub Project GitHub settings and webhook Conectar GitLab Ramas e instancias Etiquetar y filtrar proyectos Alta disponibilidad con nodos de aplicación Project environments, extensions and deletion

Instances & Console

Crear una instancia Reiniciar, detener y eliminar una instancia Fusionar ramas entre etapas Web IDE y acceso remoto SSH access to instances Explicación de los ajustes de la instancia Despliegues y la cola de trabajos

Agent Tasks

Qué son las tareas del agente Configurar las tareas del agente Ejecutar una tarea y revisar el resultado Tiempo de agente y recargas Agent insights and task filters

Monitoring & Backups

Monitorear tu instancia Copias de seguridad y restauración S3 storage, uploads and bulk backup actions Notificaciones de alerta (correo y SMS)

Workspaces & Permissions

Invitar a miembros del espacio de trabajo Permisos de los miembros y acceso a recursos Un miembro no puede ver o usar un recurso Audit log and server activity

Account & Security

Autenticación de dos factores (2FA) Ajustes de perfil e integraciones Contraseñas y recuperación de cuenta

Billing & Plans

Planes y precios Mejorar y gestionar tu suscripción Si una suscripción de proyecto queda sin pagar El programa de partners de canal Onboarding a client as a partner

Support & Tickets

Abrir un ticket de soporte Cómo obtener ayuda del equipo de CICDoo

Troubleshooting

Resolución de problemas: no se puede conectar un servidor Resolución de problemas: falló un despliegue Resolución de problemas: git push falla con 403 tras mover un repositorio Resolución de problemas: mi instancia está caída o lenta Resolución de problemas: problemas de dominio o SSL

Espacios de trabajo y permisos

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.

Anterior Un miembro no puede ver o usar un recurso

¿Sigues atascado? Abre un ticket desde la app o habla con un ingeniero.