Bindplane

The Bindplane Developer Hub

Welcome to the Bindplane developer hub. You'll find comprehensive guides and documentation to help you start working with Bindplane as quickly as possible, as well as support if you get stuck. Let's jump right in!

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

F5 Networks logs for debug messages within the authpriv facility

F5 Networks logs for informational messages within the local facility

F5 Networks logs for informational messages within the local facility

F5 Networks logs for notice messages within the cron facility

F5 Networks logs for notice messages within the cron facility

F5 Networks logs for error messages within the mail facility

F5 Networks logs for error messages within the mail facility

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

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

Logs Tab

  1. Select the Sources tab.
Sources Tab

Sources Tab

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

Add Source Configuration Button

  1. Choose F5 Networks
  2. Fill out the IP address to listen for and the port to listen on
F5 Networks Log Configuration Form

F5 Networks Log Configuration Form

F5 Networks


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.