When configuring remote high-speed logging of BIG-IP system processes, it is helpful to understand the objects you need to create and why, as described here:

1. On the Main tab, click the applicable path.
   • DNS > Delivery > Load Balancing > Pools
   • Local Traffic > Pools
   The Pool List screen opens.
2. Click Create.
   The New Pool screen opens.
3. In the Name field, type a unique name for the pool.
4. Using the New Members setting, add the IP address for each remote logging server that you want to include in the pool:
   1. Type an IP address in the Address field, or select a node address from the Node List.
   2. Type a service number in the Service Port field, or select a service name from the list.
      Note: Typical remote logging servers require port 514.
   3. Click Add.
5. Click Finished.

1. On the Main tab, click System > Logs > Configuration > Log Destinations .
   The Log Destinations screen opens.
2. Click Create.
3. In the Name field, type a unique, identifiable name for this destination.
4. From the Type list, select Remote High-Speed Log.
   Important: If you use log servers such as Remote Syslog, Splunk, or ArcSight, which require data be sent to the servers in a specific format, you must create an additional log destination of the required type, and associate it with a log destination of the Remote High-Speed Log type. With this configuration, the BIG-IP system can send data to the servers in the required format.
   The BIG-IP system is configured to send an unformatted string of text to the log servers.
5. From the Pool Name list, select the pool of remote log servers to which you want the BIG-IP system to send log messages.
6. From the Protocol list, select the protocol used by the high-speed logging pool members.
7. Click Finished.

1. On the Main tab, click System > Logs > Configuration > Log Destinations .
   The Log Destinations screen opens.
2. Click Create.
3. In the Name field, type a unique, identifiable name for this destination.
4. From the Type list, select a formatted logging destination, such as IPFIX, Remote Syslog, Splunk, or ArcSight.
   Important: ArcSight formatting is only available for logs coming from Advanced Firewall Manager™ (AFM™), Application Security Manager™ (ASM™), and the Secure Web Gateway component of Access Policy Manager^® (APM^®). IPFIX is not available for Secure Web Gateway. Remote Syslog formatting is the only type supported for logs coming from APM. The Splunk format is a predefined format of key value pairs.
   The BIG-IP system is configured to send a formatted string of text to the log servers.
5. If you selected Remote Syslog, then from the Syslog Format list select a format for the logs, and then from the High-Speed Log Destination list, select the destination that points to a pool of remote Syslog servers to which you want the BIG-IP system to send log messages.
   Important: For logs coming from Access Policy Manager^® (APM^®), only the BSD Syslog format is supported.
6. If you selected Splunk or IPFIX, then from the Forward To list, select the destination that points to a pool of high-speed log servers to which you want the BIG-IP system to send log messages.
7. Click Finished.

1. On the Main tab, click System > Logs > Configuration > Log Publishers .
   The Log Publishers screen opens.
2. Click Create.
3. In the Name field, type a unique, identifiable name for this publisher.
4. For the Destinations setting, select a destination from the Available list, and click << to move the destination to the Selected list.
   Note: If you are using a formatted destination, select the destination that matches your log servers, such as Remote Syslog, Splunk, or ArcSight.
5. Click Finished.

1. On the Main tab, click System > Logs > Configuration > Log Filters .
   The Log Filters screen opens.
2. In the Name field, type a unique, identifiable name for this filter.
3. From the Severity list, select the level of alerts that you want the system to use for this filter.
   Note: The severity level that you select includes all of the severity levels that display above your selection in the list. For example, if you select Emergency, the system publishes only emergency messages to the log. If you select Critical, the system publishes critical, alert, and emergency-level messages in the log.
4. From the Source list, select the system processes from which messages will be sent to the log.
5. In the Message ID field, type the first eight hex-digits of the specific message ID that you want the system to include in the log. Use this field when you want a log to contain only each instance of one specific log message.
   Note: BIG-IP system log messages contain message ID strings in the format: xxxxxxxx:x:. For example, in this log message: Oct 31 11:06:27 olgavmmgmt notice mcpd[5641]: 01070410:5: Removed subscription with subscriber id lind , the message ID string is: 01070410:5:. You enter only the first eight hex-digits: 01070410.
6. From the Log Publisher list, select the publisher that includes the destinations to which you want to send log messages.
7. Click Finished.

1. On the Main tab, click System > Logs > Configuration > Log Filters .
   The Log Filters screen opens.
2. Select the check box next to the name of the log filter that you want to delete. Click Delete, and then click Delete again.

1. On the Main tab, click System > Logs > Configuration > Log Filters .
   The Log Filters screen opens.
2. Click Create.
3. In the Name field, type a unique, identifiable name for this filter.
4. From the Severity list, select Debug.
5. From the Source list, select All.
6. From the Log Publisher list, select None.
7. Click Finished.