Learn how to monitor F5 BIG-IP LTM devices using the F5 LTM ActiveGate extension.


  • F5 BIG-IP LTM device(s) with iControl® API support
  • Credentials for F5 admin account or non-admin account with iControl_REST_API_User role
  • An Environment ActiveGate (version 1.155+) that has the ActiveGate plugin module installed, and isn't used for synthetic or mainframe monitoring
    • One environment ActiveGate can typically support 30-50 F5 LTM devices

Interested in monitoring F5 LTM with Dynatrace?

The quickest way to get started is by contacting a Dynatrace ONE product specialist. Just click the chat button in the upper-right corner of the Dynatrace menu bar.

Environment ActiveGate installation

ActiveGate plugin module installation

Extension installation

  1. Obtain the install file (custom.remote.python.f5.zip). Don't rename the file.

  2. Unzip custom.remote.python.f5.zip to the plugin_deployment directory of your ActiveGate host.

  3. If the resulting directory structure isn't .\plugin_deployment\custom.remote.python.f5\, please make the necessary changes.

  4. Restart the Dynatrace Remote Plugin Module service.

    • On Linux, restart the service using the following commands with admin rights:
      • systemctl restart remotepluginmodule.service
    • On Windows, run these two commands in a Command Prompt launched as Admin:
      • sc stop "Dynatrace Remote Plugin Module"
      • sc start "Dynatrace Remote Plugin Module"
  5. Return to the Dynatrace web UI. Click Settings, the Add new technology monitoring button, and finally the Add ActiveGate plugin button.

  6. Click the Upload plugin button and upload custom.remote.python.f5.zip.

  7. Enter the endpoint information requested for connecting to F5 device:

    • Endpoint name: Type a meaningful endpoint name.
    • Username: The username for connecting to the iControl® REST API (provided account must be an admin account or non-admin account with iControl_REST_API_User role)
    • Password: The account password
    • Use token authentication: Use token authentication instead of direct connection (required for LDAP-integrated and non-admin user, but may also be used with admin accounts)
      • To create a token with the User authentication API, submit a POST to https://BIG-IP-ADDRESS/mgmt/shared/authn/login including a data parameter that triggers the generation of an authentication token.
    • Hostname/IP of mgmt. interface: The hostname/IP where the mgmt. interface is listening, defaults to port 443 (HTTPS).
    • Require a valid SSL certificate: (Un)checked depending on whether or not a valid SSL certificate is required.
    • Enable debug logging: Leave unchecked by default, can be checked if requested by support for investigating an issue.
    • Comma-separated virtual servers: Allows for filtering which virtual servers should be monitored.
    • Comma-separated pools: Allows for filtering which pools should be monitored.
    • Comma-separated nodes: Allows for filtering which nodes should be monitored.
    • Comma-separated rules: Allows for filtering which rules should be monitored.
    • Comma-separated profiles: Allows for filtering which profiles should be monitored.
    • Comma-separated partitions: Allows for filtering which partitions should be monitored.
    • Name of the group: If the device is part of a cluster, type the name here to group the devices in the GUI.


Troubleshoot ActiveGate plugins

  • ActiveGate troubleshooting instructions
  • 404 error when connecting to F5?
    Starting in BIG-IP 11.6.0, a non-admin user account may be granted with the minimum permissions required to successfully query the iControl API(iControl_REST_API_User role). This role may be granted by a BIG-IP admin, using the following command: curl -sk -u <admin_username>:<admin_password> https://localhost/mgmt/shared/authz/roles/iControl_REST_API_User -H "Content-Type: application/json" -X PATCH -d '{ "userReferences":[ {"link":"https://localhost/mgmt/shared/authz/users/<username>"}


The IP address of all network interfaces and the ports used by the services are automatically captured, as are the following metrics:


  • Availability

Virtual servers (split by virtual server)

  • Status
  • Requests
  • Ephemeral/client-side connections
  • Ephemeral/client-side received bytes
  • Ephemeral/client-side transmitted bytes
  • Ephemeral/client-side received packets
  • Ephemeral/client-side transmitted packets
  • Ephemeral/client-side slow killed
  • Ephemeral/client-side evicted connections
  • CPU usage
  • Syncookie accepts
  • Syncookie rejects

Pools (split by pool)

  • Status
  • Requests
  • Connections
  • Received bytes
  • Transmitted bytes
  • Received packets
  • Transmitted packets
  • Member count
  • Current sessions

Nodes (split by node)

  • Status
  • Requests
  • Connections
  • Received bytes
  • Transmitted bytes
  • Received packets
  • Transmitted packets

Rules (split by rule)

  • Executions
  • Aborts
  • Failures

Network interfaces (split by interface)

  • Status
  • Received bytes
  • Transmitted bytes
  • Received packets
  • Transmitted packets
  • Dropped packages
  • Errors

Client and server SSL (split by profile)

  • Common connections
  • Native connections
  • Fatal alerts
  • Secure handshakes
  • Handshake failures
  • Insecure handshake accepts
  • Insecure handshake rejects
  • Insecure renegotiation rejects
  • Requests (split by protocol)

Disks (split by disks)

  • Free
  • Used
  • Reserved

CPU (split by CPUs)

  • Idle
  • IO wait
  • IRQ
  • Soft IRQ
  • Stolen
  • System
  • User


  • Total
  • Used

HTTP stats (split by profiles)

  • GET/POST requests
  • 2xx responses
  • 3xx responses
  • 4xx responses
  • 5xx responses