Applying the log monitoring
The following guides you to the basic application method for using the WhaTap log monitoring service. WhaTap log monitoring does not require configuring additional agents or applying a parser according to the logs. A simple configuration gets you started quickly.
Operating principle of log monitoring
A typical log integration service consists of the collector, processor, repository, and UI module. The process of building each module is cumbersome and additional costs are incurred because it requires step-by-step configuration and structuring.
WhaTap log monitoring is easy to apply. Because the previous monitoring agent acts as a collector, the log monitoring can be started simply by turning on the agent option.
- Java
- PHP
- Python
- Go
- Server
- Kubernetes
-
It directly collects the logs that are forwarded to the log library of your Java application rather than reading the output file.
-
Because the logs are collected directly, it does not cause file I/O so the performance impact on the system is very low.
-
You can check logs from the transaction traces by obtaining the connection traceability for transaction traces and logs.
Java log library
Representative Java log libraries are Apache Log4j and Logback.
They are available in Java Agent 2.1.1 or later.
-
The log collection function has been added to the existing agent. The monitoring agent collects by using the output logs in addition to log files.
They are available in PHP Agent 2.3.2 or later.
-
The log collection function has been added to the existing agent. The monitoring agent collects by using the output logs in addition to log files.
-
If the transaction ID is output to the log, you can check logs from the transaction traces by obtaining the connection traceability for transaction traces and logs.
They are available in Python Agent 1.2.2 or later.
-
The log collection function has been added to the existing agent. The monitoring agent collects by using the output logs in addition to log files.
-
The log collection function has been added to the existing agent. The monitoring agent collects by using the output logs in addition to log files.
They are available in Server Agent 2.1.2 or later.
-
Logs can be collected in the Kubernetes container.
-
You can collect logs from the applications in Kubernetes containers.
They are available in Kubernetes Agent 1.1.35 or later.
Applying the log monitoring
The application method according to the used application is as follows. Before application of Log Monitoring, check the supported version.
-
Check the version of the supported agent and perform update.
-
Set the options for Log Monitoring.
-
Enable the log monitoring.
Java
It explains how to collect logs from your Java application.
PHP
It guides you how to collect logs from your PHP application.
Python
It guides you how to collect logs from your Python application.
Go
It guides you how to collect logs from your Go application.
Server
It guides you how to collect logs from your server application.
Kubernetes
The following guides you through collecting logs from Kubernetes containers and the applications in Kubernetes containers.