F5 Networks

Logs Collected

Various types of logs are collected and sent to Google Stackdriver Logging. For more information around the types of logs that exist and how to configure them, please read K13317: Configuring the level of information that syslog-ng sends to log files (11.x).

The following screenshots are examples of logs that have been collected by the BindPlane Logs Agent and then sent to Google Stackdriver Logging.

F5 Networks logs for debug messages within the authpriv facility

Click to close... — F5 Networks logs for debug messages within the authpriv facility

F5 Networks logs for informational messages within the local facility

Click to close... — F5 Networks logs for informational messages within the local facility

F5 Networks logs for notice messages within the cron facility

Click to close... — F5 Networks logs for notice messages within the cron facility

F5 Networks logs for error messages within the mail facility

Click to close... — F5 Networks logs for error messages within the mail facility

Supported Versions

F5 Networks: 11.6.0+

Log Collection Setup

Pre-requisites

Follow these instructions to Configure the BIG-IP system to log to a remote syslog server (10.x - 14.x).

Configure a F5 Networks Log Source

Install the BindPlane Log Agent on the host system.
Login to BindPlane and select the Logs tab.

Screen Shot 2019-07-03 at 9.54.53 AM.png — Logs Tab

Click to close... — Logs Tab

Select the Sources tab.

Screen Shot 2019-07-03 at 9.56.25 AM.png — Sources Tab

Click to close... — Sources Tab

In the top-right portion of the screen, click on the Add Source Configuration button

Screen Shot 2019-07-03 at 10.00.25 AM.png — Add Source Configuration Button

Click to close... — Add Source Configuration Button

Choose F5 Networks
Fill out the IP address to listen for and the port to listen on

F5 Networks Log Configuration Form

Click to close... — F5 Networks Log Configuration Form

Updated about a year ago