Logging

Bitaic logging captures operational, access, agent, API, webhook, and security-relevant activity used for troubleshooting, reliability review, and audit investigations. Logging is separate from Windows Event Monitoring, which collects customer Windows Event Log entries from monitored hosts.

Log Categories

• System logs: platform service events, errors, health checks, and operational state.
• Access logs: login attempts, session starts, session endings, and authorization outcomes.
• Agent logs: agent start, stop, update, heartbeat, buffering, retry, and collection-state events.
• API and webhook logs: request IDs, delivery IDs, retry outcomes, signing errors, rate-limit outcomes, and subscription activity.
• Audit logs: Admin-visible records for security, configuration, export, deletion, token, webhook, integration, and sensitive data access events.

Retention And Export

• Active audit and monitoring history use the 12-month default retention baseline unless workspace policy or contract sets a different period.
• Webhook delivery attempts are retained for 30 days for delivery troubleshooting.
• Local agent buffers retain temporary data up to the product-specific launch cap during temporary connectivity loss.
• Supported log and audit exports use dashboard or API export flows with least-privilege permissions.

Operational Use

• Use request IDs from API responses and webhook delivery IDs to correlate logs with automation behavior.
• Review audit logs after role, token, webhook, integration, retention, export, deletion, and monitoring-configuration changes.
• Keep exported logs in storage that matches your organization's own retention and access-control requirements.