Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section III. Monitoring and Management
  4. Monitoring fluentbit
  5. Monitoring fluentbit for logging
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

Monitoring fluentbit for logging

All pods and containers that are part of the fluentbit logging system (including the fluentbit-collector, fluentbit sidecars, fluentbit Daemonsets and the Log-viewer) produce logs to stdout. These logs can be viewed via kubectl commands as described in the Table: Commands for debugging the logs or by standard log viewing and extraction options described in the 'Managing logging' chapter.

Using the following commands, you can debug the logs of the logging pods and containers:

Table: Commands for debugging the logs

Command

Usage

$ kubectl describe pod -n <netbackup namespace> <pod name>

To check the status of the pods and information about the sidecars.

$ kubectl logs -n <netbackup namespace> <pod name>

To read (view) the logs of the primary container of a pod including the fluentbit collector pod.

$ kubectl logs -n <netbackup namespace> <pod name> -c <container name>

If the container you are looking at is a sidecar you can specify the container with -c.

Note:

The appearance of some logs depends on whether the infrastructure nodes are scheduled in the nodes with NetBackup services, that are picked up by the daemonset.

Feedback

Was this page helpful?
Previous

Monitoring fluentbit

Next

Monitoring MSDP Scaleout

Feedback

Was this page helpful?