sigs.k8s.io/cluster-api-provider-azure@v1.14.3/hack/observability/readme.md (about)

     1  # Observability
     2  
     3  During development of CAPZ, it's become clear log messages can only tell part of the debugging
     4  story. As the code becomes more complex, we need better tools to help us understand what is
     5  happening in the controller.
     6  
     7  In that spirit, we've added support for metrics and tracing. This directory contains resources for
     8  development clusters to install [OpenTelemetry](https://opentelemetry.io/),
     9  [Jaeger](https://github.com/jaegertracing/jaeger-operator), and
    10  [Prometheus](https://github.com/prometheus-operator/prometheus-operator). With
    11  
    12  If you run `make tilt-up` to create your development cluster, these observability resources are
    13  installed and enabled automatically.
    14  
    15  <!-- markdown-link-check-disable-next-line -->
    16  To access traces in the Jaeger web interface, visit http://localhost:16686/ or select the
    17  "traces: jaeger-all-in-one" resource in the Tilt UI and click on "View traces" near the top of
    18  the screen.
    19  
    20  To access traces in
    21  [Application Insights](https://learn.microsoft.com/azure/azure-monitor/app/app-insights-overview),
    22  specify an `AZURE_INSTRUMENTATION_KEY` in your `tilt-settings.yaml`, then navigate to the
    23  App Insights resource in the Azure Portal and choose "Transaction search" to query for traces. See
    24  the tracing docs for more detail.
    25  
    26  <!-- markdown-link-check-disable-next-line -->
    27  To access metrics in the Prometheus web interface, visit http://localhost:9090/ or select the
    28  "metrics: prometheus-operator" resource in the Tilt UI and click on "View metrics" near the top of
    29  the screen.