---
title: "BIG-IP"
url: "https://axoflow.com/docs/axoflow/0.86/data-sources/appliances/f5/bigip/"
last_modified: "2026-05-12T12:48:47+02:00"
---

> For the complete documentation index, see [llms.txt](https://axoflow.com/docs/axoflow/0.86/llms.txt).

# BIG-IP

BIG-IP:
Provides load balancing, traffic management, and application security for optimized service delivery.

To onboard such a source to Axoflow, complete the [generic appliance onboarding steps](https://axoflow.com/docs/axoflow/0.86/data-sources/appliances/index.md).

Note that the device can be configured to send logs formatted as plain-text syslog, JSON, or key-value pairs. AxoRouter can automatically parse all flavors.

## Labels

Axoflow automatically adds the following labels to data collected from this source:

| Analytics label | Message field | Value |
| --- | --- | --- |
| `vendor` | [`meta.vendor`](https://axoflow.com/docs/axoflow/0.86/reference/message-schema/reference/index.md#meta.vendor) | `f5` |
| `product` | [`meta.product`](https://axoflow.com/docs/axoflow/0.86/reference/message-schema/reference/index.md#meta.product) | `bigip` |
| `service` | [`meta.service.name`](https://axoflow.com/docs/axoflow/0.86/reference/message-schema/reference/index.md#meta.service.name) | `ASM`, `apmd`, `audit_forwarder`, `CROND`, `F5`, `httpd`, `mcpd`, `sshd`, `sshd(pam_audit)`, `systemd-journal`, `tmm`, `tmm1`, `tmm2`, `tmsh` |

You can use the labels as:

- **Filter labels** on the [Analytics page](https://axoflow.com/docs/axoflow/0.86/metrics/analytics/index.md),
- in the **Filter By Label** field during [log tapping](https://axoflow.com/docs/axoflow/0.86/onboard-hosts/log-tapping/index.md).

You can use the message fields

- in [Flow Processing steps](https://axoflow.com/docs/axoflow/0.86/data-management/processing/index.md), for example, in the **Query** field of **Select Messages** steps,
- in AQL expressions in the search bars.

## Sending data to Splunk

When sending the data collected from this source to Splunk, Axoflow uses the following sourcetype and index settings:

| sourcetype | index |
| --- | --- |
| f5:bigip:syslog | `netops` |
| f5:bigip:ltm:access_json | `netops` |
| f5:bigip:asm:syslog | `netops` |
| f5:bigip:apm:syslog | `netops` |
| f5:bigip:ltm:ssl:error | `netops` |
| f5:bigip:ltm:tcl:error | `netops` |
| f5:bigip:ltm:traffic | `netops` |
| f5:bigip:ltm:log:error | `netops` |
| f5:bigip:gtm:dns:request:irule | `netops` |
| f5:bigip:gtm:dns:response:irule | `netops` |
| f5:bigip:ltm:http:irule | `netops` |
| f5:bigip:ltm:failed:irule | `netops` |
| nix:syslog | `netops` |

Tested with: [Splunk Add-on for F5 BIG-IP](https://splunkbase.splunk.com/app/2680/)

If the Axoflow classification doesn’t set the source field for the message automatically, and you haven’t set it in a [flow processing step](https://axoflow.com/docs/axoflow/0.86/data-management/processing/index.md#set-fields) manually (by setting the `meta.destination.splunk.source` field), AxoRouter automatically sets the source to the [name of the AxoRouter connector](https://axoflow.com/docs/axoflow/0.86/reference/message-schema/reference/index.md#meta.connector.name) that received the message (for example, `axorouter-syslog-tcp-514`).

## Sending data to Google SecOps

When sending the data collected from this source to a [*dynamic* Google SecOps destination](https://axoflow.com/docs/axoflow/0.86/destinations/google/secops/index.md), Axoflow sets the following log type: `F5_BIGIP_APM`.

## Sending data to Microsoft Sentinel

When sending the data collected from this source to a [Microsoft Sentinel destination](https://axoflow.com/docs/axoflow/0.86/destinations/microsoft/sentinel/index.md), Axoflow normalizes the data and sends it to the following table: `Syslog`.