Analyze F5 BIG-IP network, application security, and authentication logs in the context of your monitored environment.
The Dynatrace integration with F5 BIG-IP products brings network, security, and authentication logs into Dynatrace. With this additional monitoring context, you can better understand the activity in your environment and quickly identify, analyze, and report suspicious or anomalous actions.
The integration ingests:
You can forward the logs from all three modules to Dynatrace through a syslog forwarding mechanism, such as Dynatrace ActiveGate or a Bindplane agent.
This page extends the F5 BIG-IP extension page, which focuses on monitoring the logs and metrics of F5 devices.
With the ingested data, you can address the following use cases
Notebooks
Investigations
DashboardsSee below for the F5 BIG-IP and Dynatrace requirements.
An F5 BIG-IP Virtual Edition (VE) or hardware appliance with the licenses and provisioned modules for the capabilities that you use:
Administrative access to F5 BIG-IP to configure the following logging components:
ActiveGate version 1.310+ that must:
Permissions:
Extensions: Go to Hub, select
Extensions, and display Technical information.storage:logs:read.To set up the ingest of F5 BIG-IP logs, follow the steps below.
In Dynatrace, open Hub.
Look for F5 BIG-IP and select Install.
To ingest and process LTM, APM, and ASM logs, you don't need to add a monitoring configuration. Dynatrace deploys the OpenPipeline processors automatically when you install the extension.
The extension provides a pipeline that maps the logs to the Semantic Dictionary data models. For details, see Processing in OpenPipeline.
Create a dynamic route to the pipeline with the following settings:
Target pipeline: F5 BIG-IP Extension
Matching condition:
// Tagged: collector sets product.* and feature(matchesValue(product.vendor, "F5")and matchesValue(product.name, "BIG-IP")and (matchesValue(product.feature, "LTM")or matchesValue(product.feature, "ASM")or matchesValue(product.feature, "APM")))// Legacy, untagged: fixed content markersor matchesValue(content, "*product.feature=\"LTM\"*") // LTM HSL template carries its own product.* keysor matchesValue(content, "*]: 0149*") // APM message idsor matchesValue(content, "*ASM:*") // ASM CEF, CSV and key=value
Configure the logging profile for each module that you want to forward.
To collect HTTP request and response logs, configure a Request Logging profile. For details, see Configuring Request Logging in the F5 documentation.
In F5 BIG-IP, go to Local Traffic > Profiles > Other > Request Logging.
Turn on request and response logging, select mds-udp, and configure a dedicated logging pool that points to the ActiveGate syslog receiver (UDP port 5513 in this example).
Add the following request and response log templates, and associate the profile with the application virtual server.
Request log template (F5-side metadata):
event_source="request_logging",hostname="$BIGIP_HOSTNAME",client_ip="$CLIENT_IP",server_ip="$SERVER_IP",http_method="$HTTP_METHOD",http_uri="$HTTP_URI",http_host="${host}",virtual_name="$VIRTUAL_NAME",event_timestamp="$DATE_HTTP"
Response log template (F5-side metadata):
event_source="response_logging",hostname="$BIGIP_HOSTNAME",client_ip="$CLIENT_IP",server_ip="$SERVER_IP",http_method="$HTTP_METHOD",http_uri="$HTTP_URI",http_host="${host}",virtual_name="$VIRTUAL_NAME",http_statcode="$HTTP_STATCODE",event_timestamp="$DATE_HTTP"
You can add identification fields, such as product.name, directly to the LTM log templates.
If you also forward ASM and APM logs, keep the enrichment fields only in the syslog receiver configuration (see the following steps).
If you ingest only LTM logs, you can add the fields to the F5 BIG-IP profile and skip the receiver configuration in ActiveGate. Add the following fields to the templates:
product.vendor="F5",product.name="BIG-IP",product.feature="LTM",connection_id="<DYNATRACE_CONNECTION_ID>"
Replace <DYNATRACE_CONNECTION_ID> with the connection_id that the Dynatrace platform provides. If no connection_id is provided, remove it.
Follow the instructions in Turn on syslog ingestion.
Connect to the F5 BIG-IP command line and run:
tmsh list sys ntp timezone
Example output:
sys ntp {timezone America/Los_Angeles}
Note the time zone. Use it as the location value of the ASM and APM receivers.
Add one receiver for each F5 BIG-IP module. For details about custom attributes, see Add custom attributes.
Connect to the ActiveGate host and open the syslog configuration file:
sudo nano /var/lib/dynatrace/remotepluginmodule/agent/conf/syslog.yaml
Copy and paste the configurations for the modules that you use into the existing receivers: section. Keep the existing receivers.
This receiver collects HTTP request and response logs over UDP port 5513.
receivers:syslog/f5-big-ip-ltm:udp:listen_address: "0.0.0.0:5513"add_attributes: trueprotocol: noneoperators:- type: syslog_parserprotocol: none- type: addfield: attributes["product.vendor"]value: "F5"- type: addfield: attributes["product.name"]value: "BIG-IP"- type: addfield: attributes["product.feature"]value: "LTM"- type: addfield: attributes["connection_id"]value: "<DYNATRACE_CONNECTION_ID>"
Before you save the file:
<DYNATRACE_CONNECTION_ID> placeholders with the connection_id that the Dynatrace platform provides. The ID uniquely identifies the ingest traffic. If no connection_id is provided, remove this attribute.<DEVICE_LOCATION> with the time zone that you noted in the previous step. For example, America/Los_Angeles.Use three separate receivers with different ports, one for each F5 BIG-IP module. Separate receivers make it easier to identify and monitor the ingested logs.
In the same syslog.yaml file, add the following pipelines to the existing service.pipelines section:
service:pipelines:logs/f5-big-ip-ltm:receivers: [syslog/f5-big-ip-ltm]processors: [transform, attributes, batch]exporters: [otlphttp/syslog]logs/f5-big-ip-asm:receivers: [syslog/f5-big-ip-asm]processors: [attributes, batch]exporters: [otlphttp/syslog]logs/f5-big-ip-apm:receivers: [syslog/f5-big-ip-apm]processors: [attributes, batch]exporters: [otlphttp/syslog]
Keep the existing processor definitions and the Dynatrace exporter configuration unchanged. The LTM pipeline requires the transform processor to preserve the raw KVP log content.
Save the configuration and apply the changes according to your ActiveGate version.
To verify the syslog ingestion configuration, run the following command on ActiveGate:
sudo grep -R "Otel syslog enabled" \/var/lib/dynatrace/remotepluginmodule/log/extensions/ \| tail -n 10
Expected output:
Otel syslog enabled: true
After you configure the log forwarding, and as soon as F5 BIG-IP generates logs, verify that Dynatrace ingested them into Grail. Run the following queries in
Notebooks, or explore the logs in
Logs.
HTTP traffic logs:
fetch logs| filter log.type == "f5-big-ip-ltm"| sort timestamp desc
After the setup, you can query and analyze the F5 BIG-IP logs in Grail with
Notebooks and
Dashboards.
For more information, see Syslog ingestion with ActiveGate and OpenPipeline.

The integration collects logs from F5 BIG-IP LTM, ASM, and APM through syslog forwarding with Dynatrace ActiveGate or a Bindplane agent. After you configure the integration:
/api/v2/logs/ingest). For details, see OpenPipeline ingest sources.
Investigations,
Notebooks,
Dashboards, and other apps, such as For billing information, see Log Management and Analytics.
Yes. You can use a Bindplane agent as an alternative to the ActiveGate syslog ingestion.
For log matching and mapping to work, enrich the logs with the following attributes in the Bindplane processing steps:
product.vendorproduct.nameproduct.featureconnection_id Optional