Traceable supports multiple deployment setups to monitor and secure API traffic across different environments. However, support for third-party API monitoring varies depending on the deployment method. This topic describes which deployment configurations support third-party API monitoring and explains the available capabilities for each configuration.
Note
Traceable supports F5 Load Balancer, Boomi, Gloo, Daemonset Mirroring (non-Linux/Windows Mirroring Agent), Avi Vantage, Ambassador, OpenResty, and 3scale using the eBPF Agent or the Mirroring Agent. Other gateways, load balancers, and proxies are also supported through these agents.
The following table lists supported deployment setups and indicates whether third-party API monitoring is supported or not:
Deployment Setup | Third-Party API Monitoring |
|---|---|
eBPF | Yes |
Mirroring Agent | No |
AWS API Gateway | No |
Mulesoft Mule Gateway | Yes |
Mulesoft Flex Gateway | Yes |
Akamai Edgeworker | No |
Akana | No |
Apigee | Yes |
AWS Lambda Runtime Extension | No |
Axway | Yes |
Azure APIM | No |
CA Layer7 | No |
Cloudflare Worker | No |
CloudFront Lambda | No |
Fastly Compute@Edge | Yes |
F5 HSL | No |
Golang | Yes |
HAProxy | No |
IBM APIC | Yes |
IBM DataPower | Yes |
IIS | No |
Istio | Yes |
Java | Yes |
KGateway | No |
Kong | No |
.NET | Yes |
Netlify | No |
Netscaler (Citrix) | No |
NGINX | Yes |
Node.js | Yes |
Python | Yes |
Ruby | Yes |
Traceable Edge | No |
Traefik | No |