F5BigLogProfile¶
Overview¶
The F5BigLogProfile Custom Resource (CR) is used to specify traffic processing events that the Traffic Management Microkernel (TMM) should capture, and send to one or more remote logging servers. The F5BigLogProfile specifically handles events that occur when TMM is processing traffic with any of the Protection BIG-IP Next for Kubernetes CRs. The F5BigLogHslpub CR specifies the remote logging destination IP address and service port, and the logging format. The F5BigLogHslpub CR should be configured and installed first, and then referenced in the F5BigLogProfile CR configuration.
Parameters¶
metadata¶
Parameter |
Description |
|---|---|
|
The unique name identifying the resource (Kubernetes object name). Example: |
|
The Kubernetes namespace in which the resource is created. |
spec¶
Parameter |
Description |
Default |
Support for BIG-IP Next for Kubernetes (DPU) |
|---|---|---|---|
|
Specifies the user defined name for the log profile. This name is used to identify and reference the log profile configuration within the system. |
|
Yes |
|
Specifies the name of the log publisher used for logging events. The publisher defines where and how log messages are sent and processed. |
|
Yes |
|
Specifies the Network Address Translation (NAT) logging configuration. This includes settings for enabling NAT logging, LSN legacy mode, subscriber ID logging, rate limiting, and publisher name. |
|
No |
|
Specifies the firewall logging configuration. This section controls various firewall-related logging features including network events, port misuse, IP intelligence, and traffic statistics. |
|
Yes |
|
Enables or disables DNS logging. If enabled, DNS query and response messages are logged. |
|
No |
|
Specifies the configuration for protocol inspection logging. Protocol inspection provides detailed analysis and logging of network protocols for security monitoring and troubleshooting purposes. |
|
No |
|
Specifies the configuration for Application Layer Gateway (ALG) logging. ALG logging provides detailed information about application-specific protocol handling and connection management. |
|
No |
|
Specifies the configuration for Policy Enforcement (PE) logging. PE logging provides detailed information about policy enforcement decisions and actions for traffic monitoring and compliance reporting. |
|
No |
firewall¶
Parameter |
Description |
Default |
|---|---|---|
|
Specifies whether to enable or disable firewall logging. When enabled, firewall events will be logged according to the configured settings. |
|
|
Specifies the configuration for logging Flowspec events. |
|
|
Specifies the configuration for logging IP Intelligence events. |
|
|
Enables or disables logging of traffic statistics events. |
|
|
Specifies the configuration for logging port misuse events. |
|
|
Specifies the configuration for logging network firewall events. |
|
|
Specifies whether to enable or disable firewall logging. When enabled, firewall events will be logged according to the configured settings. |
|
|
Specifies the name of the log publisher used for logging Firewall Flowspec events. |
|
|
Specifies the configuration for logging IP Intelligence events. IP Intelligence provides threat detection based on IP reputation and geographic location. |
|
|
Specifies the name of the log publisher used for logging IP Intelligence events. |
|
|
Enables or disables logging of the geo location for IP intelligence shun events. |
|
|
Enables or disables logging of the Remote Triggered Black Hole (RTBH) events. |
|
|
Enables or disables logging of IP intelligence scrubber events. |
|
|
Enables or disables logging of IP intelligence shun events. |
|
|
Enables or disables logging of IP intelligence translation events. |
|
|
Specifies a rate limit for all combined IP Intelligence log messages per second. |
|
|
Enables or disables logging of the number of active flows on the client side. The number of flows is logged globally, per virtual server and per route domain periodically if the number of active flows increases or decreases. |
|
|
Enables or disables logging of the number of active flows on the client side. |
|
|
Enables or disables logging of the number of reaped flows on the client side. |
|
|
Enables or disables logging of the number of TCP packets (non SYN/ACK) that were dropped because the flow table lookup failed. |
|
|
Enables or disables the logging of the number of syncookies generated, accepted, and rejected globally and per virtual server. |
|
|
Enables and disables logging of the number of syncookies whitelist hits, accepted and rejected globally and per virtual server. |
|
|
Specifies the name of the log publisher to use to log traffic statistics. |
|
|
Specifies the configuration for logging port misuse events. Port misuse detection helps identify when ports are being used for unauthorized or suspicious activities. |
|
|
Specifies the name of the log publisher used for logging port misuse events. |
|
|
Specifies a rate limit for all combined port misuse log messages per second. |
|
|
Specifies the configuration for logging network firewall events. This includes ACL matches, IP errors, TCP events, and various network-related logging settings. |
|
|
Specifies the name of the log publisher used for logging network events. |
|
|
Specifies a rate limit for all combined network log messages per second. |
|
|
Specifies the network events to be logged. The default is to log all events. |
|
|
Specifies the rate limits for different types of network events. |
|
|
Specifies the format for network log messages. |
|
|
Specifies the network events to be logged. |
|
|
Enables or disables the logging of packets that match ACL rules configured with the actions Accept or Accept Decisively. |
|
|
Enables or disables the logging of packets that match ACL rules configured with the action Drop. |
|
|
Enables or disables the logging of packets that match ACL rules configured with the action Reject. |
|
|
Specifies to enable or disable the logging of IP error packets. |
|
|
Specifies to enable or disable the logging of TCP error packets. |
|
|
Specifies to enable or disable the logging of TCP events. |
|
|
Specifies to enable or disable the logging of translation fields in network log messages. |
|
|
Specifies to enable or disable the logging of user information in network log messages. |
|
|
Enables or disables the logging of Geographic IP location information fields in ACL match and TCP logging. |
|
|
Enables or disables the logging of the ACL rule UUID field in ACL match and ACL match and TCP logging. |
|
|
Enables or disables the logging of traffic that is coming to management IP address. If drop or reset log is already enabled, enabling this field creates one more log. |
|
|
Specifies the rate limits for different types of network events. These limits control how many log messages per second are generated for each event type. |
|
|
Rate limit for the logging of packets that match ACL rules configured with the actions Accept or Accept Decisively. |
|
|
Rate limit for the logging of packets that match ACL rules configured with the action Drop. |
|
|
Rate limit for the logging of packets that match ACL rules configured with the action Reject. |
|
|
Specifies the rate limit for the logging of IP error packets. |
|
|
Specifies the rate limit for the logging of TCP error packets. |
|
|
Specifies the rate limit for the logging of TCP events. |
|
|
Specifies the format for network log messages. |
|
|
Specifies the format type for network log messages. |
|
|
Specifies user-defined field list for custom network logging format (for example, |
|
|
Specifies the network field list configuration for network log messages. |
|
|
Specifies the delimiter character used to separate fields in the network log message output for proper formatting. |
|
|
Specifies the individual fields to be included in the network log messages for detailed logging information. |
|
Sample CRs for F5BigLogHslpub and F5BigLogProfile¶
Install the F5BigLogHslpub CR:
apiVersion: k8s.f5net.com/v1
kind: F5BigLogHslpub
metadata:
name: hsl-publisher
namespace: f5-bnk
spec:
pool:
-
name: hsl-pool
endpoint:
- 11.19.10.100:514
syslog:
-
name: syslog
format: rfc5424
protocol: tcp
pool: hsl-pool
Install the F5BigLogProfile CR:
apiVersion: k8s.f5net.com/v2
kind: F5BigLogProfile
metadata:
name: "logprofile"
namespace: f5-bnk
spec:
publisher: "hsl-publisher"
firewall:
enabled: true
network:
events:
aclMatchAccept: true
aclMatchDrop: true
aclMatchReject: true
Attach the LogProfile to Gateway/GatewayClass/Gateway Listener in SecPolicy CR.
apiVersion: "gateway.k8s.f5.com/v1alpha1"
kind: SecPolicy
metadata:
name: secpolicy-global
namespace: f5-bnk
spec:
extensionRefs:
- kind: F5BigLogProfile
name: logprofile
group: k8s.f5net.com
targetRefs:
- kind: GatewayClass
name: f5-gateway-class
group: gateway.networking.k8s.io
The log message indicates that the F5BigLogProfile CR was added/updated:
kubectl create -f logprofile.yaml
f5biglogprofile.k8s.f5net.com/logprofile created
kubectl get -f logprofile.yaml
NAME READY MESSAGE AGE
logprofile True CR config sent to all grpc endpoints 2s
kubectl describe -f logprofile.yaml
..
Status:
Conditions:
Last Transition Time: 2026-03-18T13:41:02Z
Message:
Observed Generation: 0
Reason: Accepted
Status: True
Type: Accepted
Last Transition Time: 2026-03-18T13:41:02Z
Message: CR config sent to all grpc endpoints
Observed Generation: 2
Reason: Programmed
Status: True
Type: Programmed
Generation Id: 0
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Added/Updated 22s f5-cne-controller LogProfile alpha/logprofile was added/updated
F5BigLogProfile: Example of user-defined field list¶
apiVersion: "k8s.f5net.com/v1"
kind: F5BigLogProfile
metadata:
name: "log-profile"
namespace: f5-bnk
spec:
firewall:
enabled: true
network:
publisher: "hsl-publisher"
events:
aclMatchAccept: true
aclMatchDrop: true
aclMatchReject: true
translationFields: true
format:
type: user-defined
userDefinedFieldList: "DateTime:${date_time},Host:${bigip_hostname},MgmtIP:${management_ip_address},FwPolicy:${acl_policy_name},SrcIP:${src_ip},SrcPort:${src_port},DstIP:${dest_ip},DstPort:${dest_port},TrSrcIP:${translated_src_ip},TrDstIP:${translated_dest_ip},TrSrcPort:${translated_src_port},TrDstPort:${translated_dest_port},Protocol:${protocol},Action:${action},Context:${context_name}"
F5BigLogProfile: Example of field-list¶
apiVersion: "k8s.f5net.com/v1"
kind: F5BigLogProfile
metadata:
name: "log-profile"
namespace: f5-bnk
spec:
firewall:
enabled: true
network:
publisher: "hsl-publisher"
events:
aclMatchAccept: true
aclMatchDrop: true
aclMatchReject: true
translationFields: true
format:
type: field-list
networkFieldList:
delimiter: ";"
items:
- "date_time"
- "bigip_hostname"
- "management_ip_address"
- "acl_policy_name"
- "src_ip"
- "src_port"
- "dest_ip"
- "dest_port"
- "translated_src_ip"
- "translated_dest_ip"
- "translated_src_port"
- "translated_dest_port"
- "protocol"
- "action"
- "context_name"