Audit

The Audit page is a single place to see all actions done in QIP by users or the system. It gives important information for:

• Following safety rules (compliance),
• Making operations clear and visible.

This tool helps admins track every change in the platform. You can:

• See who did what and when,
• Check actions if problems happen (like security issues),
• Make sure everyone is responsible for their work.

---

Key Tracking Capabilities

QIP captures four core action types across all system entities:

• Create: Records new object initialization (e.g., chains, snapshots).
• Update: Tracks configuration modifications (e.g., chain edits, variable changes).
• Delete: Logs removal of resources (e.g., folders, deployments).
• Read: Monitors data access events (e.g., export operations, configuration reviews) (only for export) .

These actions apply to three primary entity categories:

1. Workflow Elements

• Structural Components: Folders, individual chains, or chain groups.
• Deployment Artifacts: Snapshots, snapshot cleanup events, and active deployments.
• Runtime Elements: Workflow elements, masked fields, and chain runtime properties.

2. Service Integrations

• Discovery & Configuration: Service discovery operations and external/internal service definitions.
• Environment Management: Cloud services (inner/implemented), environments and specifications.
• Specification Hierarchy: Specifications, specification groups, and detailed design templates.

3. Security & Configuration Assets

• Secrets Management: Kubernetes secrets, secured/common variables.
• Messaging Systems: Managed Kafka/RabbitMQ (Maas) configurations.
• Operational Resources: Import instructions and templates.

---

User Interface Overview

Accessed via Admin Tools → Audit, the interface features a customizable table with these default columns:

• Action Time: Timestamp of the event.
• Initiator: User triggering the action.
• Operation: Action type (Create/Update/Delete/Read).
• Entity Type: Category of affected object (e.g., Chain, Specification).
• Entity Name: Specific object identifier.
• Parent Name: Hierarchical context.

Users can:

• Toggle column visibility to focus on relevant data (e.g., hide Parent Name for simple audits).
• Export action logs for external compliance reporting.
• Refresh to view real-time activity during incident investigations .