Skip to main content

Log FAQs

Check out frequently asked questions from users about the WhaTap log monitoring service.


Restoration of the original log

Can I recover the original logs after collecting them?

The function to restore the original logs is not provided. Currently, log collection is provided for analysis, not for security.

Log data deletion cycle

What is the log data deletion cycle?

It is the same as Data retention set in Log Configuration. However, because the loaded log retention period is in hours, data may remain for 1 hour in addition to the setting in Data retention.

Note

If Data retention has not been set, the default value is 1 day. For more information about the setting in Data retention, see the following.

Agent logs transmission cycle

What is the log transmission cycle from the agent?

Logs are sent when the agent's log buffer capacity (64 KB) or transmission cycle (2 seconds) is reached. It is compressed in a zip file and transmitted during network transmission, and is decompressed and stored when received from the collection server.

Integrating with third-party log solutions

Can it integrate with other log solutions?

Currently, integration with third-party log solutions is not provided.

Log Collection by Platform

How can I collect logs for applications, servers, and Kubernetes?

Log collection by platform is as follows.

JAVA

The logs are collected by hooking in the log4j and logback log libraries.

Note

When using logback or log4j, you may need to set options for Appender-based log collection. For more information, see the Open source tracing document in WhaTap Docs.

Node.js

By hooking the built-in package process of Node.js, the logs for process.stdout and process.stderr are collected.

Python

The logs are collected by hooking in the logging and loguru log libraries.

PHP / Server

Collection is made by specifying the log files to monitor.

Go
  • Collection is made by specifying the log files to monitor.

  • The Standard out and Standard error logs are collected for applications.

Note

To collect logs for standard outs and errors, extra settings are required.
For more information, see the Go Monitoring > API Guide document in WhaTap Docs.

Kubernetes
  1. Container StdOut

    The WhaTap Kubernetes agent collects Container's standard output logs (Container stdout/stderr). These logs are collected using two methods, depending on the purpose of use.

    • Logfile-based collection

      This method directly reads log files stored in the file system of the Kubernetes node.
      The collected logs can be checked using the Log > Log Trend, Log Search, and Live Tail features.

      WhaTap agent log file collection path
      /var/log/pods/<namespace>_<pod-name>_<uid>/<container-name>/*.log
      Example
      /var/log/pods/whatap_agent_7ddf2a4c-0877-4602-a38c-df07c4501ede/agent/0.log
      Caution

      If logs are not collected, connect to the node and then check if the log files exist in the above path. For more information about the log collection filters, see the Kubernetes Monitoring > Log document in WhaTap Docs.

    • Real-time lookup via kube-apiserver

      When you click a specific container in the container map, the Kubernetes API (kube-apiserver) is called in a way similar to the kubectl logs command to load the container logs in real time.

      This method is useful for quickly checking the container status, but it does not provide the search or long-term retention feature.

      TypeLog tabClick Container Map > Container
      Collection methodsDirect access to the node's file systemCall the kube-apiserver API
      Log location/var/log/pods/<namespace><pod-name><uid>/<container-name>/*.logCall the kube-apiserver API
      Use caseSearch, Filtering, Live TailCheck real-time status
      RetentionOX (Real-time view only)
  2. K8s Event

    The Kubernetes event collection logs are collected after checking via the kubectl get events.

Note

How to Configure Logs

For the log configuration method, see the contents for each platform (e.g. JAVA, Node.js) in Log Monitoring of WhaTap Docs.