Application Monitoring is the Google Cloud solution for application observability. Application Monitoring creates dashboards for your [App Hub](https://docs.cloud.google.com/app-hub/docs/overview.md.txt) applications, services, and workloads. It also displays a topology view of your application. To understand which resources your application uses and how those resources interact, you use App Hub. To understand how your application's resources are performing and to diagnose issues, you use Application Monitoring.

<br />

## What is Application Monitoring?

Application Monitoring provides the services you need to monitor your applications and
the resources and infrastructure they use, from the perspective of your
application. That is, you don't begin an investigation by searching your
resources and figuring out which resources your application uses. Instead, you
begin an investigation with your application, and then find information about
the resources and infrastructure that it uses. The dashboards and topology graph
that Application Monitoring generates for your application let you understand the
operational state of your application and its services and workloads.

Application Monitoring creates a dashboard for your application that shows
more detailed information, like golden signals, log data, and information
about open alerts:

![Dashboard that lists the golden signals and logs for an application.](https://docs.cloud.google.com/static/stackdriver/images/aco-app-dashboard-tab.png)

Application Monitoring also lets you view the topology of your application. The
topology graph can help you visualize your workloads and services, and the traffic
between them:

![The application topology graph provides a graphical representation of your workloads and services.](https://docs.cloud.google.com/static/stackdriver/images/aco-app-topology.png)

## Why you should adopt Application Monitoring

Using Application Monitoring can save you time and effort. For example, suppose you
use the [Application Design Center](https://docs.cloud.google.com/application-design-center/docs/overview.md.txt)
to help you design and deploy your application. Next, you use
App Hub to help you organize and manage that application. To understand
the performance of your application and to diagnose failures,
you use Application Monitoring, which features the following:

- Dashboards that list your application, service, and workload data.

- A topological view of your application that visualizes traffic.

- The ability to filter your telemetry data by criticality and environment.

Once your application is deployed, the Application Monitoring service
discovers your application and automatically builds dashboards tailored
to your environment. To support your investigation of alerts, these
dashboards support search and filtering.

The dashboards that Application Monitoring creates display the following:

- Information about the application, such as the location, criticality, and
  owners.

- Information about open alerts.

- Log and metric data generated by
  [supported infrastructure](https://docs.cloud.google.com/stackdriver/docs/observability/application-monitoring-services.md.txt).
  The metric data includes golden signals, like error rates and traffic, and
  select metrics.

- Trace data generated by
  [instrumented applications](https://docs.cloud.google.com/stackdriver/docs/observability/instrument-for-application-monitoring.md.txt#add_application_attributes_to_trace_spans).
  This data includes span and service names, latency information, and error
  rates.

When your application runs on supported infrastructure, Application Monitoring
automatically attaches application-specific labels to telemetry data
that your application generates. These labels identify your
App Hub application. You can use these application-specific
labels when querying your telemetry data. The **Logs Explorer** ,
**Metrics Explorer** , and **Trace Explorer** pages let you use
labels to filter and aggregate data.

## Get started with Application Monitoring

To use Application Monitoring, do the following:

1. [Create your application and register services and workloads to the application](https://docs.cloud.google.com/app-hub/docs/overview.md.txt).
   Alternatively, you can deploy your application by using the
   [Application Design Center](https://docs.cloud.google.com/application-design-center/docs/overview.md.txt).

2. Configure the observability scope so that you can view the telemetry for your
   application. For information about this step, see
   [Set up Application Monitoring](https://docs.cloud.google.com/stackdriver/docs/observability/setup-application-monitoring.md.txt).

3. If you want your application-generated metric and trace data to include
   application labels, then instrument your application with OpenTelemetry or use
   Google Cloud Managed Service for Prometheus. For more information, see
   [Instrument app for Application Monitoring](https://docs.cloud.google.com/stackdriver/docs/observability/instrument-for-application-monitoring.md.txt).

   > [!NOTE]
   > **Note:** For workloads that run on Google Kubernetes Engine, the dashboards that Application Monitoring creates display OpenTelemetry-defined metrics for traffic, latency, and error rate golden signals.

4. Open and explore the Application Monitoring dashboards. For information about viewing
   these dashboards, see [View application telemetry](https://docs.cloud.google.com/stackdriver/docs/observability/application-monitoring.md.txt).

5. View a topological graph of your application. For more information, see
   [View application topology](https://docs.cloud.google.com/stackdriver/docs/observability/application-topology.md.txt).