Audit Trail

3 min read

KubeOps
Audit Trail
Security & Compliance

BP’s Audit Trail #

The BuildPiper Audit Trail feature provides complete visibility into user and system activities across the platform. It records key actions such as login events, configuration changes, pipeline updates, deployment activities, permission modifications, and integration changes โ€” ensuring transparency, accountability, and traceability for all operations performed within BP.

1 GB
Log Storage Limit
6
Setup Steps
Full
Activity History
Audit
Ready

Audit Trail Configurations #

Set up and configure the Audit Trail feature within BuildPiper to begin capturing platform activity.

01
Prerequisites
System Setting Flag

Before using the Audit Trail feature, the following system-level flag must be enabled by an administrator.

โ–ธNavigate to System Settings โ†’ Audit Logs
โ–ธEnable the Audit Logs Enable option
โ–ธSelect the HTTP request methods to track: GET POST PUT DELETE
๐Ÿ’ก Admin only: This flag can only be configured by users with system administrator access.
Audit Trail System Setting Flag

How the Feature Works #

01
Enable Audit Logs
System Settings โ†’ Audit Logs

Navigate to System Settings โ†’ Audit Logs and enable the Audit Logs Enable option. Select the HTTP request methods (GET, POST, PUT, DELETE, etc.) that should be tracked.

02
User Activity Monitoring
Tracks all user and system actions

Once enabled, BP starts monitoring user and system actions automatically.

โ–ธLogin attempts
โ–ธConfiguration updates
โ–ธPipeline modifications
โ–ธDeployments and API calls

03
Log Entry Creation
Structured log format per activity

For every tracked activity, BP generates a structured log entry in the following format:

Log Format

[Timestamp] [HTTP METHOD] [LEVEL] [USER_NAME] [URL] [BODY] [OTHER_PARAMETERS]

04
Log Storage
Stored on filesystem

All audit logs are stored in the following directory on the BuildPiper host:

Log Directory

/var/log/buildpiper/audit_trail/forensic_date.logs

05
Data Size Control
Storage capped at 1 GB

The audit log storage is limited to 1 GB to ensure efficient disk utilization and prevent excessive storage consumption.

๐Ÿ’ก Storage tip: Monitor log size periodically. Once the 1 GB limit is reached, older logs may be rotated or overwritten.

06
Review and Compliance
Audit, investigate, and govern

Administrators can review logs to maintain governance and meet compliance requirements.

โ–ธTrack system changes and configuration history
โ–ธInvestigate incidents and unexpected behaviour
โ–ธEnsure accountability across all user actions
โ–ธMeet security and compliance requirements
โœ… By maintaining a detailed activity history, BP enables organisations to monitor platform usage and maintain controlled, auditable CI/CD workflows.

BP Hands-On #

Practical guidance for accessing and using the Audit Trail feature inside BuildPiper.

01
Navigation
How to access Audit Records

Follow the steps below to access the Audit Trail inside BuildPiper:

1

Login to BP using Admin credentials

2

Select Audit Records from the left-side navigation panel

๐Ÿ’ก Admin access required: Only users with Admin credentials can access the Audit Records section.
Audit Trail Navigation Screenshot

02
Search & Filters
Find and identify modified entities

Users can apply various filters available in the UI to search and identify BuildPiper entities that have been modified or updated by users during day-to-day operations.

By User
Filter activities performed by a specific user account.
By Date Range
Narrow down logs within a specific time window.
By Action Type
Filter by HTTP method โ€” GET, POST, PUT, DELETE.
By Entity
Search for changes to a specific pipeline, config, or resource.
โœ… Filters help teams quickly pinpoint which user made a change, what was changed, and when โ€” reducing investigation time significantly.

๐Ÿ“˜ BuildPiper Documentation ยท Audit Trail

Last updated: March 2026