OpenTelemetry Protocol

Related topics

• Google-Built OpenTelemetry Collector works with OpenTelemetry Protocol From the official documentation: “It lets you send correlated [OpenTelemetry Protocol (OTLP)](https://opentelemetry.io/docs/specs/otlp/) traces, metrics, and logs to Google Cloud Observability and other backends from applications.”
• OpenTelemetry collector works with OpenTelemetry Protocol From the official documentation: “The OpenTelemetry `Collector` sends log, metric, and trace data to your project by using the Telemetry API, which uses OTLP.”
• Google Cloud Observability works with OpenTelemetry Protocol From the official documentation: “Google Cloud Observability supports ingesting log, metric, and trace data in OTLP format.”
• OpenTelemetry Protocol works with OpenTelemetry SDK From the official documentation: “This example app is configured to use the OpenTelemetry Python SDK to export logs, metrics, and traces by using the [OTLP protocol](https://opentelemetry.io/docs/specs/otlp/).”
• OpenTelemetry Protocol works with OpenTelemetry SDKs From the official documentation: “The [OpenTelemetry SDKs](https://opentelemetry.io/docs/languages/) generate log, metric, and trace data in a format that is generally consistent with the proto files defined by the [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otlp).”
• OpenTelemetry Protocol works with Ops Agent From the official documentation: “* Collection of [OpenTelemetry Protocol (OTLP) metrics and traces](/stackdriver/docs/solutions/agents/ops-agent/otlp) from applications instrumented with [OpenTelemetry SDKs](https://opentelemetry.io/docs/instrumentation/).”
• OpenTelemetry Protocol works with Telemetry (OTLP) API From the official documentation: “Log, metric and trace data is sent to Google Cloud by using the [Telemetry (OTLP) API](/stackdriver/docs/reference/telemetry/overview), which implements the [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otlp).”
• Compute Engine works with Ops Agent From the official documentation: “In Compute Engine VMs, the Ops Agent can collect logs and most metrics.”
• Cloud Logging works with Ops Agent From the official documentation: “Is the agent sending logs to Cloud Logging?”
• Google Cloud Observability is an alternative to Prometheus From the official documentation: “You can enable metrics export to Prometheus instead of Stackdriver (now called Google Cloud Observability) on GKE on Google Cloud clusters.”
• Cloud Monitoring works with Ops Agent From the official documentation: “Is the agent sending metrics to Cloud Monitoring?”
• Google-Built OpenTelemetry Collector works with Google Cloud Observability From the official documentation: “The Google-Built OpenTelemetry Collector sends metrics, logs, and traces from your instrumented applications to Google Cloud Observability.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Logging works with Cloud Trace From the official documentation: “To identify requests with high latency using Cloud Logging, apply the `traceSampled=true` filter to correlate logs in Cloud Logging with traces in Cloud Trace.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• Cloud Run works with Google Cloud Observability From the official documentation: “Cloud Run automatically uses Google Cloud Observability to aggregate and review your logs, as described in the [logging page](/run/docs/logging).”
• Cloud Run works with OpenTelemetry collector From the official documentation: “Set up the [OpenTelemetry Collector as a sidecar agent in Cloud Run](/run/docs/tutorials/custom-metrics-sidecar).”
• Cloud Trace is an alternative to OpenTelemetry collector From the official documentation: “To send traces to an external managed tracing backend or a self-hosted OpenTelemetry Collector instead of Cloud Trace:”
• Cloud Trace works with Ops Agent From the official documentation: “If you have configured the Ops Agent to collect traces, but you get no traces in Cloud Trace when you run your application, then you might need to grant an additional role to the Compute Engine service account the agent uses.”
• Google Cloud Observability works with OpenTelemetry collector From the official documentation: “The Google-Built OpenTelemetry Collector sends metrics, logs, and traces from your instrumented applications to Google Cloud Observability.”
• Google Cloud Observability works with Ops Agent From the official documentation: “This guide explains how to ensure that the Ops Agent, which you install on your virtual machine (VM) instance, is authorized to send telemetry data to Google Cloud Observability.”
• Ops Agent depends on Compute Engine From the official documentation: “The agents run only on Compute Engine VMs; these procedures apply only to that platform.”
• Ops Agent works with Prometheus From the official documentation: “Starting with version 2.46.0, the Ops Agent includes the VM name as part of the `namespace` label when ingesting metrics in the Prometheus ingestion format.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging is an alternative to Cloud Trace From the official documentation: “You can use Cloud Trace or Cloud Logging to understand how long a particular request has taken.”
• Cloud Logging is part of Google Cloud Observability From the official documentation: “Logging is enabled by default, and belongs to Google Cloud Observability.”
• Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
• Cloud Monitoring is part of Google Cloud Observability From the official documentation: “PHP libraries are available for the following Stackdriver services: - [Error Reporting](#error_reporting) - [Cloud Logging](#logging) - [Cloud Monitoring](#monitoring)”
• Cloud Monitoring works with Google Cloud Observability From the official documentation: “To develop effective alerting and monitoring dashboards and mechanisms, use [Google Cloud Observability](/stackdriver/docs) tools together with [Cloud Monitoring](/monitoring/docs/monitoring-overview).”
• Cloud Monitoring works with Prometheus From the official documentation: “When you configure Prometheus with [Stackdriver Prometheus sidecar (deprecated)](https://github.com/Stackdriver/stackdriver-prometheus-sidecar), metrics exported by Prometheus are converted to Cloud Monitoring metric types with simple [metric…”
• Cloud Monitoring is an alternative to Prometheus From the official documentation: “Configure your own alerting policies in Cloud Monitoring or in Prometheus for issues affecting your workloads or local environment.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run works with Google-Built OpenTelemetry Collector From the official documentation: “To install the Google-Built OpenTelemetry Collector as a sidecar for your Cloud Run, first create a secret to store the collector's configuration.”
• Cloud Trace is part of Google Cloud Observability From the official documentation: “Ruby libraries are available for the following Google Cloud Observability services: - [Error Reporting](#error_reporting) - [Logging](#logging) - [Monitoring](#monitoring) - [Trace](#trace)”
• Compute Engine works with Google-Built OpenTelemetry Collector From the official documentation: “This document shows how to run the [Google-Built OpenTelemetry Collector](/stackdriver/docs/instrumentation/google-built-otel) on Compute Engine to collect OTLP logs, metrics, and traces from instrumented applications and then export that data to Google Cloud.”
• OpenTelemetry collector works with Ops Agent From the official documentation: “Combining the collection of logs, metrics, and traces into a single process, the Ops Agent uses [Fluent Bit](https://fluentbit.io/) for logs, which supports high-throughput logging, and the [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) for metrics and…”
• OpenTelemetry collector is an alternative to Ops Agent From the official documentation: “In addition, Compute Engine and Google Kubernetes Engine environments capture and include trace data when they use the Ops Agent or the OpenTelemetry Collector.”
• OpenTelemetry collector works with Telemetry (OTLP) API From the official documentation: “This document describes how to deploy the OpenTelemetry Collector, configure the collector to use the `otlphttp` exporter and the [Telemetry (OTLP) API](/stackdriver/docs/reference/telemetry/overview), and run a telemetry generator to write metrics to Cloud Monitoring.”
• OpenTelemetry SDKs works with Ops Agent From the official documentation: “* Collection of [OpenTelemetry Protocol (OTLP) metrics and traces](/stackdriver/docs/solutions/agents/ops-agent/otlp) from applications instrumented with [OpenTelemetry SDKs](https://opentelemetry.io/docs/instrumentation/).”
• Ops Agent is part of Cloud Monitoring From the official documentation: “Cloud Monitoring offers a [Ops Agent](/monitoring/agent) that collects additional disk, CPU, network, and process metrics from your VM instances.”
• Ops Agent depends on OpenTelemetry collector From the official documentation: “The Ops Agent is the primary agent for collecting telemetry from your Compute Engine instances. Combining the collection of logs, metrics, and traces into a single process, the Ops Agent uses [Fluent Bit](https://fluentbit.io/) for logs, which supports high-throughput logging…”