Deploy OpenTelemetry on Google Cloud C4A Axion processors
Introduction
Get started with OpenTelemetry on Google Axion C4A
Create firewall rules on GCP for Flask and observability components
Create a Google Axion C4A Arm virtual machine on GCP
Set up OpenTelemetry environment and application on Arm64
Deploy the OpenTelemetry observability stack on Arm64
Next Steps

  Log an issue

  Fork and edit

  Discuss on Discord

About this Learning Path

Skill level:  Introductory
Reading time:  40 min
Last updated:  20 Feb 2026
Skill level:
  Introductory
Reading time:
  40 min
Last updated:
  20 Feb 2026
Author:Pareena Verma, Arm
Arm IP:Neoverse
Tags: Performance and Architecture Google Cloud Linux Flask Docker Prometheus Jaeger
Author:
  • Pareena Verma, Arm
Arm IP:
Neoverse
Tags:
Performance and Architecture Google Cloud Linux Flask Docker Prometheus Jaeger

Who is this for?

This learning path is for DevOps engineers, platform engineers, and software developers who want to deploy and observe a cloud-native microservice on Arm64-based Google Cloud C4A Axion processors using OpenTelemetry.

What will you learn?

Upon completion of this Learning Path, you will be able to:

  • Deploy an instrumented Python Flask microservice on Google Cloud C4A Axion processors
  • Configure OpenTelemetry Collector to process and route distributed traces and metrics
  • Integrate Prometheus and Jaeger for comprehensive metrics collection and distributed tracing visualization
  • Generate and analyze telemetry data to monitor application performance on Arm-based infrastructure

Prerequisites

Before starting, you will need the following:

  • A Google Cloud Platform (GCP) account with billing enabled
  • Basic familiarity with Python and Flask
  • Basic understanding of containers and Kubernetes concepts
Next