How to: Access the BIG-IP Next Central Manager application logs¶

The BIG-IP Next Central Manager application log aggregates log entries generated by the various microservices that make up the application.

Summary¶

Use this procedure and the command line interface (CLI) to access the BIG-IP Next Central Manager audit logs. Currently, access to these logs is only available using the CLI and the fluentd service.

Prerequisites¶

Access to the Kubernetes Pods that house the BIG-IP Next Central Manager for which you want to view the application logs.

Procedures¶

Access the BIG-IP Next Central Manager application logs
Application log examples

Access the BIG-IP Next Central Manager application logs¶

Use the following procedure to view the application logs for BIG-IP Next Central Manager.

Log in (via SSH or the console) to the virtual machine (VM) on which your BIG-IP Next Central Manager resides.
Type the following command to display the BIG-IP Next Central Manager application logs:
```
kubectl logs mbiq-fluentd-0 fluentd | grep nats.fluent_log
```
The application logs for BIG-IP Next Central Manager will display.
To display a continuously updating list of BIG-IP Next Central Manager application logs, you can add the -f switch.
For example:
```
kubectl logs mbiq-fluentd-0 fluentd -f | grep nats.fluent_log
```
The application logs for this BIG-IP Next Central Manager virtual machine will display; and any new actions on this virtual machine will display as well.

For examples of the kind of information a typical application log entry provides, refer to Application log examples.

Application log examples¶

Each log entry has one of the following levels:

trace
debug
info
warning
error
fatal
panic

The log level communicates the severity of the log entry… ranging from normal execution (informational) to failure. Here are a few entries followed by an explanation of the kind of information you can extract from them.

Example log entries:

{“action”:””,”level”:”error”,”msg”:”DEVICE-00017: Unable to find device group”,”source”:”Device DeviceModel”}
{“action”:”Created device group”,”level”:”info”,”msg”:”DEVICE-00016: Successfully created a device group : default”,”source”:”Device DeviceModel”}
{“action”:”Login”,”level”:”info”,”msg”:”Login succeeded for user admin”,”source”:”Gateway Authentication”}

Action	Level	Description
Get device group	Error	Unable to find device group
Created device group	Information	Successfully created a device group
Login	Information	Login succeeded for user admin

Previous Next