How jenkinsci/audit-trail-plugin works
Main Components
a) Core Plugin Components:
• AuditTrailPlugin (Central coordinator)
• AuditTrailFilter (HTTP request interceptor)
• AuditTrailRunListener (Build events listener)
• CredentialUsageListener (Credentials usage tracker)
b) Logger Implementations:
• ConsoleAuditLogger
• LogFileAuditLogger
• LogFileDailyRotationAuditLogger
• SyslogAuditLogger
• ElasticSearchAuditLogger
c) External Systems:
• Jenkins Core
• File System
• Syslog Server
• Elasticsearch Server
• Console Output
Input Layer
• Jenkins HTTP requests
• Build triggers
• Credential usage events
Processing Layer
• AuditTrailFilter
• AuditTrailRunListener
• CredentialUsageListener
Core Layer
• AuditTrailPlugin (central component)
Output Layer
• Various logger implementations
• External systems
Specific Elements
• Rectangles: Core components
• Hexagons: External services
• Rounded rectangles: Listeners and filters
• Blue: Core plugin components
• Green: Input sources
• Orange: Logger implementations
• Gray: External systems
• Event flow from input sources
• Data flow to logging destinations
• Configuration flow
Relationships to Highlight
• How AuditTrailPlugin coordinates with different loggers
• Demonstrate the event capture flow from Jenkins to logging destinations
• Configuration relationships
Additional Details
A notes section showing:
• Supported log formats
• Configuration options
• Security considerations (like IP address limitations)
Event capture mechanisms
Keep the abstraction level focused on the architectural components while showing the plugin's core functionality of capturing and logging Jenkins operations through various output channels.