Troubleshoot Application Monitoring
Stay organized with collections Save and categorize content based on your preferences.

This document contains information that might help you understand the what data is displayed on the Application monitoring page. It also contains information that might help you configure your Google Cloud project so that you can view your application's data.

Known issues

This section lists known issues related to Application Monitoring:

Trace latency isn't available in Application Monitoring. You must use the Trace Explorer page to view your trace data. For more information, see Find and explore traces.

Troubleshoot

This section describes how to resolve issues related to Application Monitoring.

You are told to create an application

You open the Application monitoring page in the Google Cloud console and see the message "Create an Application to get started". You don't expect to see this message because you've registered an App Hub application.

To resolve this failure, ensure that the resource picker is set to your App Hub host project.

Your application doesn't show data for some golden signals

There are several reasons why you won't see a value for a golden signal:

The infrastructure doesn't support the metric type. For example, Network Load Balancers don't support system metrics. For more information, see App Hub supported resources.
The metric type is supported, but there isn't any data available. For example, if the time range is set for an interval when no metric data was collected, then there isn't data to display for the golden signals.

For a list of resources which generate App Hub labels, see App Hub supported resources.

Your application's metric data is missing or incomplete

You view a chart for a service or workload, and this chart either doesn't show any metric data or some data is missing.

You might not need to do anything. The charts added to the predefined dashboard for a service or workload are selected based on the resources used by that service or workload. However, some resources might not generate data for a specific metric type. For a list of resources which generate App Hub labels, see App Hub supported resources

If the metric data is incomplete, then do the following:

Make sure that the project picker is set to your App Hub host project.
Make that the organization administrator has configured the metrics scope for your App Hub host project to list the projects that store your application's metric data. For more information, see Set up Application Monitoring.

Your application's log data is missing or incomplete

The logs panel on a dashboard doesn't show any log entries or it doesn't show all log entries that are generated by your application.

To resolve this failure, do the following:

To get the permissions that you need to view log data, ask your administrator to grant you the following IAM roles:
- Logs Viewer (roles/logging.viewer) on your App Hub host project and any other projects listed its default log scope. This role grants access to most log entries in the _Default log bucket. For more information, see Logging roles.
- Logs View Accessor (roles/logging.viewAccessor) on the log views listed in the default log scope of your App Hub host project. To learn more about granting access to a log view, see Control access to a log view.
Ensure that the organization administrator has configured the default log scope of your App Hub host project to list the resources that store your application's log data. For more information, see Set up Application Monitoring.

Your alerting policies are missing

For an alerting policy to be shown on an Application Monitoring dashboard, you must associate the alerting policy with a service or workload by adding specific labels to the policy.

To associate an alerting policy with a workload or service by using the Google Cloud console, do the following:

In the Google Cloud console, go to the Alerting page:
Go to Alerting

If you use the search bar to find this page, then select the result whose subheading is Monitoring.
In the toolbar of the Google Cloud console, select your App Hub host project.
Find the alerting policy, click View more, select Edit, and then go to the Notifications and name section.
In the Application labels section, select your application and then select your workload or service.
Click Save policy.

After you complete these steps, labels with the following keys are attached to your alerting policy. These labels identify your application and your service or workload:

apphub_application_location
apphub_application_id
apphub_application_container
apphub_service_id or apphub_workload_id

You can also add user labels to an alerting policy by using the Google Cloud CLI, Terraform, or the Cloud Monitoring API. However, you must use the label keys shown in the previous example. For more information, see the following:

You've added application labels to your alerting policy, but the policy isn't listed

To resolve this failure, verify that the policy includes the following labels:

apphub_application_location
apphub_application_id
apphub_application_container
apphub_service_id or apphub_workload_id

The dashboards for your services and workloads differ

There is no action to take.

The resources used by a service or workload determine what data is displayed for that service or workload.

You can't save changes to the dashboard you are viewing

You are exploring data shown in a service or workload dashboard and you want to save your changes. The toolbar displays a Save to dashboard button. However, when you select that button, you can't save the changes to your current dashboard.

The Save to dashboard button is shown only when the dashboard you are viewing is read-only. However, you can use this button to save your changes to a custom dashboard. For more information, see Dashboards overview.

You can't save your chart

When you are exploring telemetry data, in the toolbar, the Save to dashboard button is disabled.

To resolve this failure, ensure that you have sufficient permissions.

To get the permissions that you need to save changes to a custom dashboard, ask your administrator to grant you the Monitoring Editor (roles/monitoring.editor) IAM role on your App Hub host project.

Unexpected incidents are being opened

With the release of Application Monitoring, the metadata.system_labels.apphub_host_project_id label was renamed as metadata.system_labels.apphub_application_container. This change might result in some new incidents being generated and some open incidents not closing. For example, for metric-absence policies, you might get notified because the change in labels might cause a monitored time series to stop reporting samples.

There is no action to take. Incidents close automatically when data stops arriving, after the auto-close duration expires. For more information, see Partial metric data.