Skip to main content

Documentation Index

Fetch the complete documentation index at: https://tyk.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

Tyk Cloud supports three types of observability data:
  • Distributed Traces: Track request flow, identify bottlenecks, and troubleshoot issues.
  • Gateway Metrics: Export RED (Rate, Error, Duration) metrics to monitor API performance.
  • Application Logs: Stream application logs in real time to your configured provider.
Traces and metrics are available for Cloud Data Plane deployments. Logs can be enabled for both Control Plane and Cloud Data Plane deployments. This feature is built on Tyk Gateway’s OpenTelemetry integration. See the OpenTelemetry documentation for configuration options and sampling strategies.
Telemetry is an add-on feature in Tyk Cloud. Contact our support team to enable it for your account.

Available Telemetry Providers

Tyk Cloud integrates with:

Instructions

Configuring telemetry is a two-step process:
  1. Configure a provider at the organization level.
  2. Enable telemetry export on a Cloud Data Plane.

Step 1: Configure a telemetry provider

  1. In the Tyk Cloud Console, select Telemetry. A grid shows all supported providers.
    Only one provider can be configured at a time.
    Tyk Cloud Telemetry providers
  2. Click your preferred provider to open its configuration form.
  3. Configure the following settings shared by all providers:
    • Connection Toggle: Activates or deactivates telemetry export. When enabled, Tyk sends monitoring data to your chosen platform.
    • Sampling Rate: Percentage of API traffic to send (default: 10%, meaning one in every ten API calls).
  4. Optionally configure:
    • Tags to Add to the Traces: Custom labels that make telemetry data easier to filter and analyze. For example:
      environment: production
      region: europe
      team: api-gateway
      
    • Fields to Filter: Fields to exclude from telemetry, useful for preventing sensitive data from reaching your monitoring platform.
  5. Configure the provider-specific connection settings:

Step 2: Enable telemetry export on a Cloud Data Plane

Changes to telemetry settings require a Cloud Data Plane redeployment to take effect.
  1. Navigate to your Cloud Data Plane deployment (create new or edit existing).
  2. In the telemetry export section, enable the types you want: Tyk Cloud Telemetry Enable
    • Enable Traces: Enable distributed tracing.
    • Enable Metrics: Enable gateway metrics export (requires Gateway v5.13.0 or later). See Default Metrics Exported for what is included.
    • Enable Logs: Enable real-time application log streaming.
  3. If traces are enabled, optionally set a Sampling Rate Override to control what percentage of trace data to export (default: 10%). This setting applies to traces only — not metrics or logs.
    The sampling rate can be set at the organization level and overridden per Cloud Data Plane. The Cloud Data Plane setting takes precedence.
  4. Save and redeploy the Cloud Data Plane.
  5. In the deployment overview, confirm that Telemetry Export shows as enabled: Tyk Cloud Data Plane Telemetry Enabled

Default Metrics Exported

When metrics are enabled, Tyk exports the following RED (Rate, Error, Duration) metrics by default:
MetricDescriptionExample Values
HTTP MethodHTTP method used in the requestGET, POST, PUT, DELETE
API IDUnique identifier of the APIapi-12345
HTTP Response CodeHTTP status code returned200, 404, 500
Metrics are exported using OpenTelemetry’s cumulative temporality model, which tracks the total count of events over time.
Metric customization (additional dimensions, filtering) is not self-service. Submit a support request at support.tyk.io to configure custom dimensions.Custom metric dimensions can significantly increase cardinality, which affects gateway memory usage and your observability platform’s storage costs.