Events vs Logs to Store Audit Logs
Fleeting- External reference: https://signoz.io/comparisons/opentelemetry-events-vs-logs/
Event Use Cases
- User Actions: Tracking specific user interactions like clicks, form submissions, or feature usage. For example, capturing when a user logs in or clicks a “Buy Now” button.
- State Changes: Recording changes in application or system state, such as order status updates or configuration changes. For example, tracking when an order moves from “Pending” to “Shipped.”
- Performance Monitoring: Capturing start and end times of critical operations for precise timing analysis. For example, measuring how long it takes for an API call to complete.
Log Use Cases
- Debugging: Detailed error messages and stack traces for troubleshooting. For example, Logging a stack trace when an exception occurs during order processing.
- Compliance: Maintaining audit trails of system access and data modifications. For example, Logging each time a user accesses sensitive data or modifies a critical setting.
- System Health: Ongoing records of resource utilization, uptime, and general system status. For example, Logging memory consumption and system load over time to detect potential issues.
— https://signoz.io/comparisons/opentelemetry-events-vs-logs/ ()
Security and audit logs, meanwhile, record access patterns, authentication attempts, and other critical information necessary to identify security breaches and ensure compliance with regulatory requirements
Use Logs to capture detailed error messages and stack traces from our service, along with any key internal activity for the service, and any information that may be required for audit/security purposes. Logs should be structured and contain high-cardinality attributes that are excluded from metrics.
— https://chronosphere.io/learn/logs-vs-metrics-vs-traces/ ()