<aside> 🔔 This is generated documentation; DO NOT EDIT. / Generated by: Update Handbook GitHub Action / Last updated: 2024-09-28T07:09:53Z / Generated from: sourcegraph/managed-services@b149888

</aside>

This document describes operational guidance for Telemetry Gateway infrastructure. This service is operated on the Managed Services Platform (MSP).

If you need assistance with MSP infrastructure, reach out to the Core Services team in #discuss-core-services.

<aside> 🚨 Due to Notion limitations, we currently recreate the contents of each page entirely on updates. This means you cannot share links to sections within these pages, as the linked blocks will not persist - sourcegraph/notionreposync#7 tracks future improvements to this mechanism.

</aside>

Service overview

• Service ID: telemetry-gateway (specification)
• Owners: core-services
• Service kind: Cloud Run service
• Environments:
  • dev
  • prod
• Docker image: us.gcr.io/sourcegraph-dev/telemetry-gateway
• Source code: github.com/sourcegraph/sourcegraph - cmd/telemetry-gateway

The Telemetry Gateway service is the service that ingests telemetry v2 events from all Sourcegraph instances, as well as other managed services.

• For Sourcegraph instances that prior to 5.2.0, no events are exported to Telemetry Gateway, though legacy mechanisms may exist, e.g. for Cloud instances.
• As of 5.2.0, certain flags can be configured to export events that have been instrumented with the new APIs to Telemetry Gateway.
• As of 5.2.1, for existing licenses, export is enabled by default for Cody events only - for new licenses, export is enabled for all events. Some license tags can be configured to disable telemetry export in various degrees - see the original Telemetry Export rollout plan.

For discussion around telemetry V2 adoption, please reach out to #wg-v2-telemetry.For discussion around the Telemetry Gateway service, please reach out to #discuss-core-services.For more information, also see:

• Service API: telemetrygateway.proto