Logs (Global)
The Logs page in the Kubeark Platform provides users with access to detailed application and audit logs, as well as the ability to export these logs for further analysis or record-keeping. The application logs provide information on the actions and events that occur within the platform, while the audit logs track changes made to the platform's configuration and user management. These logs can be viewed and filtered on the Logs page, and can also be exported in various file formats for further analysis or record-keeping.
To access the platform logs, go to the Audit section of the main feature menu and select Logs.
ο»Ώ
Here three types of logs are available:
- Audit Logs
- Platform Logs
- Exported Logs
Kubeark provides a detailed list of actions that have been performed within the platform, including:
- Description: A brief description of the action that was performed.
- Changed Values: The specific values that were changed as a result of the action.
- IP Address: The IP address of the device or user that performed the action.
- User Agent: The browser or application used to perform the action.
- Created: The date and time the action was performed.
This list of actions can be found on the Logs page of the Kubeark Platform and can be filtered and searched to find specific actions. It provides a comprehensive view of all the actions that have been performed within the platform, allowing users to track and troubleshoot any issues that may have arisen. The information provided in the list of actions is useful for monitoring platform activity, auditing changes and troubleshooting issues. It also allows administrators to see what actions were performed by which user and when.
Platform logs offer a detailed record of all the actions and events that occur within the Kubeark Platform. These logs include a wide range of information that can be used to track and troubleshoot any issues that may arise within the platform.
The Kubeark Platform uses a system of logging levels to categorize and prioritize different types of events and messages that are recorded in the application logs. These levels are used to indicate the severity of the event or message, with higher levels indicating more severe issues. The logging levels used in the Kubeark platform include:
- Critical: This level is used to log events that are critical to the operation of the system and that may result in system failure or data loss if not addressed immediately. These events are considered the most severe and require immediate attention.
- Error: This level is used to log events that indicate an error or problem has occurred within the system. These events may not result in immediate system failure or data loss, but they may cause issues if left unaddressed.
- Warning: This level is used to log events that may indicate a potential problem or issue within the system. These events may not result in immediate system failure or data loss, but they should be monitored and addressed as needed.
- Info: This level is used to log events that provide general information about the operation of the system. These events are not considered errors or warnings and are typically used to track the normal operation of the system.
- Debug: This level is used to log detailed information about the system's operation that may be useful for debugging and troubleshooting issues. This level is generally intended for developers and system administrators.
These logging levels are used to prioritize and filter the log events in real-time, and also for further analysis. They make it easy for users to quickly identify and address critical issues, while also providing detailed information for troubleshooting and debugging purposes.
The specific elements included in the application logs may vary depending on the specific implementation of the Kubeark Platform, but typically include the following:
Attribute | Description |
|---|---|
LoggerΒ | The logger refers to the unique identifier associated with each log event or message recorded in the application logs of the Kubeark Platform. This identity is used to identify the specific source or origin of the log event, and can be used to filter and search through the logs to find specific events. |
Level | -> Critical-> Error-> Warning-> Info-> Debug |
Message | A brief message or description of the log event. This attribute typically provides a summary of the event or action that occurred and provides context for the log event. |
Trace | A detailed trace or stack trace of the log event. This attribute provides a more in-depth view of the event, including the specific steps and actions that led to the event, which can be useful for debugging and troubleshooting. |
The Exported Logs page in the Kubeark Platform is designed to provide users with a comprehensive view of all the logs that have been exported from the system. This page lists all the exported logs and provides users with the ability to export new audit logs by clicking on the "Create a new exported audit log" button.
Users can filter the list of exported logs by date, log type, and log level, making it easy to find the specific logs they need. They can also view the details of each exported log, including the log message, trace, username, IP address, HTTP request, and creation date.
Additionally, the exported logs can be downloaded in various file formats, such as CSV, JSON, and XML, for further analysis or record-keeping. This feature allows users to keep a record of the platform's activity, troubleshoot issues, and perform compliance and auditing activities.
Exported logs can be used for troubleshooting, compliance, and auditing purposes. They provide a comprehensive view of all the actions that have been performed within the platform, allowing users to track and troubleshoot any issues that may have arisen. These exported logs give users the flexibility to analyze the data in the format that suits them best.
