Audit

The Audit application provides centralized logging of events across Doc Gen. It enables tracking of user actions, system events, and integrations, supporting monitoring, troubleshooting, and compliance requirements.

Audit data can be accessed in three different ways depending on your use case:

1. Audit Application (UI) – For interactive inspection and manual analysis
2. Audit API – For programmatic access and integrations
3. Audit Log Forwarding – For exporting logs to external systems (e.g., SIEM or logging platforms)

Accessing Audit Data

Audit Application (UI)

The Audit application is accessible from the Doc Gen start page and provides a user interface for browsing and analyzing audit events.

Purpose

• View and search audit logs
• Investigate user activity and system events
• Perform manual troubleshooting

Home

The Home view displays the most recent audit entries.

Features

• Summary tiles showing event distribution over the last 30 days
• Quick access to filtered event lists via View links
• Chronological list of recent audit entries

Steps

1. Open Audit from the Doc Gen start page
2. Review the summary tiles for a high-level overview
3. Click View on a tile to filter events
4. Click an event name to inspect detailed information

Search

The Search view allows advanced filtering of audit records.

Features

• Filter by Source, Level, and Date range
• Free text search across events

Steps

1. Navigate to Search in the Audit application
2. Apply filters:
   • Source
   • Level
   • Date range
3. Enter optional search text
4. Click Search
5. Select an entry to view details

Audit Entry Details

Each audit entry contains standardized metadata describing the event.

Standard Fields

Audit API

The Audit API enables programmatic access to audit data, allowing integration with external systems, automation tools, or custom dashboards.

Purpose

• Retrieve audit logs for reporting or monitoring
• Integrate audit data into external systems
• Automate analysis and alerting

Usage

Audit data can be retrieved using the provided API endpoints.

Typical Use Cases

• Fetch audit logs for a specific time range
• Filter events by source, user, or severity
• Build dashboards or monitoring tools
• Correlate audit data with external systems

General Steps

1. Authenticate using Centerpoint API credentials
2. Call the relevant Audit API endpoint
3. Apply filters (e.g., date range, source, level)
4. Process the returned data in your system

Audit Log Forwarding

Audit Log Forwarding allows automatic export of audit events to external systems such as logging platforms or SIEM solutions (e.g., Elastic).

Purpose

• Centralize logs across multiple systems
• Enable real-time monitoring and alerting
• Support compliance and auditing requirements

Configuration

Audit Log Forwarding is configured in the Administration application.

Steps

1. Open Administration
2. Navigate to Integrations → Audit Log Forwarding
3. Select forwarding method:
   • Console (for testing/debugging)
   • REST API (for external systems)
4. Configure endpoint and required authentication
5. Save the configuration

Important Behavior

Audit log forwarding uses a fire-and-forget mechanism.

Implications

• No retry logic is implemented
• Failed deliveries are not resent
• Delivery failures must be handled by the receiving system

Recommendations

• Ensure high availability of the receiving endpoint
• Implement monitoring and logging on the receiving system
• Do not rely on forwarding as the only source of audit data

When to Use Each Method