Logs Collection and Forwarding

TIBCO OI Hawk RedTail - Container Edition can collect logs from Kubernetes pods, services, deployments etc. In case if TIBCO OI Hawk RedTail - Container Edition is deployed on Docker environment, then it can collect logs from Docker containers and then forwards these logs to LogLogic® Log Management Intelligence (LMI). Once these logs are forwarded to LogLogic® LMI, the user can configure LogLogic LMI remotely and perform search operations on these logs. Moreover, the user can also use the Grafana data source ‘LogLogic’ to display the logs from remote LogLogic LMI into dashboard panels. For more information, see TIBCO® Operational Intelligence Hawk® RedTail - Container Edition User Guide.

Kubernetes Logs Collection

TIBCO OI Hawk RedTail - Container Edition can collect logs from a Kubernetes cluster if TIBCO OI Hawk RedTail - Container Edition is deployed on Kubernetes. To collect logs, you must configure a collector and a forwarder so that, the logs can be forwarded to LogLogic LMI. The user can specify the namespace, controller type and controller name to collect the logs from. The supported controller types are Deployments, ReplicaSet, StatefulSets and DaemonSet. When a particular controller is selected for log collection, the log is collected from all pods deployed by the controller. The log which is forwarded to the  LogLogic LMI machine contains the container name, pod name, pod IP, namespace name, Cluster name and the actual log. For example, if a ReplicaSet is selected for log collection, then the logs are collected from all the replica pods of selected ReplicaSet.

Docker Logs Collection

TIBCO OI Hawk RedTail - Container Edition can collect logs from a Docker container if TIBCO OI Hawk RedTail - Container Edition is deployed on Docker. To collect logs, you must configure a collector and a forwarder so that, the logs can be forwarded to  LogLogic LMI. The user can specify the container name to collect the logs from.