GCP Cloud Trace Sampling Builder

MonitoringGCP

Build Cloud Trace sampling configurations with per-service overrides and propagation format settings.

Cloud Trace Configuration

Build Cloud Trace sampling configurations with per-service overrides, URL filters, and propagation format settings.

Required Fields

projectIdtracingConfig.samplingRate

{
  "projectId": "my-project",
  "tracingConfig": {
    "samplingRate": 0.1,
    "maxNumberOfAttributes": 32,
    "maxNumberOfAnnotations": 32,
    "maxNumberOfMessageEvents": 128,
    "maxNumberOfLinks": 32
  },
  "overrides": [
    {
      "service": "api-service",
      "samplingRate": 0.5,
      "description": "Higher sampling for API service for detailed latency analysis"
    },
    {
      "service": "payment-service",
      "samplingRate": 1.0,
      "description": "Full sampling for payment flows"
    },
    {
      "service": "batch-worker",
      "samplingRate": 0.01,
      "description": "Low sampling for high-volume batch jobs"
    }
  ],
  "urlFilter": {
    "excludePatterns": [
      "/healthz",
      "/readyz",
      "/_ah/health",
      "/metrics"
    ]
  },
  "exportConfig": {
    "destination": "CLOUD_TRACE",
    "enableOpenTelemetry": true,
    "otlpEndpoint": "",
    "batchSize": 200,
    "scheduledDelayMillis": 5000
  },
  "propagation": {
    "type": "W3C_TRACE_CONTEXT",
    "additionalFormats": ["B3_MULTI_HEADER", "CLOUD_TRACE"]
  }
}

Generated Output

Output will appear here...

Overview

Build Cloud Trace sampling configurations with per-service overrides and propagation format settings. This tool helps GCP engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

How Engineers Use This

•Designing a Cloud Trace Sampling configuration for a new GCP workload where the team wants the spec reviewed before any console click happens.
•Building a Cloud Trace Sampling reference implementation for a partner integration where you cannot rely on console access.
•Drafting a Cloud Trace Sampling change for a Terraform or Config Connector module before raising the pull request, so reviewers see intent in plain text.
•Sketching a Cloud Trace Sampling migration across GCP projects or folders with the org-policy implications called out.

Questions & Answers

Can the output of this Cloud Trace Sampling builder be checked into source control safely?

Yes. The output is plain text containing only configuration — no Google Cloud credentials, project IDs (unless you typed them), or secrets are included. Treat it like any other infrastructure-as-code artifact: review in pull requests, gate on validation, apply via your change process.

Can I use this Cloud Trace Sampling builder for Google Cloud sovereign or assured workloads?

Most Cloud Trace Sampling primitives behave the same in standard, Assured Workloads, and sovereign Google Cloud deployments, but available services, regions, and access controls differ. The output is portable in shape; you must verify service availability and any Assured Workloads constraints before applying in a controlled environment.

Related Learning Guides

Firestore Data Modeling26 min read
Cost Optimization Guide24 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.