Log Levels and Filtering
Overview
Log levels and filtering are critical for analyzing API traffic logs using Kibana.
Kibana is an interface program used to visualize and analyze Elasticsearch data. Filtering can be done by log levels using Kibana and focus can be placed on specific log types.
Log Levels
Log levels used in Apinizer are as follows:
Error logs contain critical issues and system errors. Logs at this level indicate situations requiring urgent intervention.
Warning logs contain potential issues and situations that need attention. Logs at this level are important for preventive maintenance.
Information logs contain general system activities and informative messages. Logs at this level are used to track system status.
Debug logs contain detailed technical information. Logs at this level are used in troubleshooting and development processes.
Filtering Options
Various filtering options can be used in Kibana:
You can view logs in a specific time range. You can select predefined ranges such as last 15 minutes, last 1 hour, last 24 hours, or custom time ranges.
You can filter logs at specific log levels. For example, you can view only logs at ERROR level.
You can filter logs belonging to a specific API Proxy. This is useful for analyzing the performance and errors of a specific API.
You can filter by HTTP status codes. For example, you can view only requests with 500 error codes.
Filtering Use Cases
You can analyze system errors by filtering logs at ERROR level. You can detect specific errors with time range and API Proxy-based filtering.
You can monitor performance metrics by filtering logs at INFO and WARN levels for a specific API Proxy.
You can access detailed technical information and perform troubleshooting operations by filtering logs at DEBUG level.
You can detect security violations and unauthorized access attempts by filtering by status code.
Related Topics
You can review the following pages for more detailed information: