Log types :: Kloudfuse Docs
Log types
Depending on the system or application that generates them, logs vary in format and content. Kloudfuse handles the following types of logs:
Application logs
Capture application-specific events and errors.
Example: User interactions within an application.
System logs
Monitor system-level events and errors, and record operating system events.
Examples: Startup messages, system changes, critical system errors, events, unexpected shutdowns, errors and warnings, and other important processes.
Security logs
Record security-related events for analysis and response.
Example: Intrusion detection alerts, anti-virus scans.
Firewall logs
Provide information on allowed and denied network traffic.
Example: Recording incoming/outgoing connections.
Server logs
Contains a record of activities related to a specific server during the specified period of time.
Event logs
High-level logs that record information about network traffic and usage.
Example: Login attempts, failed password attempts, and application events.
Change logs
Include a chronological list of changes made to an application or file.
Network logs
Track network activities and detect unusual patterns.
Example: Network traffic threats.
Threat logs
Contain information about system, file, or application traffic that matches a predefined security profile within a firewall.
Access logs
Record requests made to a server, including information about the request and the server’s response. Can be used to monitor application performance, identify threats, and discover problems.
They include a list of people or bots that access specified applications or files.
Audit logs
Keep a record of all significant events for compliance and accountability.
Example: Logging user actions, system changes.
Authentication logs
Track user login and logout activities.
Example: User login success and failure logs.
Resource logs
Provide information about connectivity issues and capacity limits.
Authorization logs
Record actions taken by privileged administrators.
They include a list of people or bots that access specified applications or files.
Example: User roles or permissions logging changes.
Availability logs
Track system performance, uptime, and availability.
Container logs
Record standard output and error streams produced by a running containerized application. Monitor and troubleshoot an application’s performance and functioning.
Database logs
Monitor database transactions and identify potential issues.
Examples: Logging SQL queries, and changes to the database.
Endpoint logs
A record of events that occur on a device used by an end user.
Examples: May include information such on system events, software installations, registry changes, logon and session activity, and alerts generated after a failed procedure deployment or a breach of monitoring conditions.
Web service logs
Record all activity on a web server over a specific time period. They contain information about the server’s requests, errors, and other activities.