[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-04 (世界標準時間)。"],[],[],null,["# Viewing your microservices\n\nCloud Monitoring provides a dashboard that summarizes all your\nservices, the **Services Overview** dashboard. The **Services Overview**\ndashboard is also the entry point for other service-monitoring tasks.\n\nThis page describes the summary information on the **Services\nOverview** dashboard of the Google Cloud console. From this dashboard, you can do\nthe following:\n\n- See the status of your services, and drill down into any one for additional\n details.\n\n- Modify the configuration of services:\n\n - For services on Cloud Service Mesh, Istio on Google Kubernetes Engine, and App Engine, you can define service-level objectives (SLOs) using standard availability and latency metrics.\n - For custom services, you can do the following:\n - Create new custom services.\n - Identify metrics to act as service-level indicators (SLIs).\n - Define SLOs based on those SLIs.\n - Set up alerting policies to notify you when performance does not meet the SLOs.\n\n For information on configuration tasks, see the following:\n - [Defining a custom service](/stackdriver/docs/solutions/slo-monitoring/ui/define-svc).\n - [Creating an SLO](/stackdriver/docs/solutions/slo-monitoring/ui/create-slo).\n - [Creating an SLO-based alerting policy](/stackdriver/docs/solutions/slo-monitoring/ui/create-alert).\n\nYou can also use the Monitoring API to manage services\nprogrammatically. For more information, see [Using the API](/stackdriver/docs/solutions/slo-monitoring/api/api-structures).\n\nBefore you begin\n----------------\n\nTo understand service monitoring, you need to be familiar with concepts like\nservice-level indicators (SLIs), SLOs, error budgets, and SLO-based alerting\npolicies. These concepts are described on other pages, for example:\n\n- For an introduction to SLIs, SLOs and error budgets, see [Concepts in\n service monitoring](/stackdriver/docs/solutions/slo-monitoring).\n\n- For an introduction to SLO-based alerting policies, see\n [Alerting on your burn rate](/stackdriver/docs/solutions/slo-monitoring/alerting-on-budget-burn-rate).\n\nServices Overview dashboard\n---------------------------\n\nThe **Services Overview** dashboard provides a summary view of all the services\nin your project, including basic information about the health of those services.\n\nIn the Google Cloud console, go to the\n**SLOs** page:\n\n[Go to **SLOs**](https://console.cloud.google.com/monitoring/services)\n\n\u003cbr /\u003e\n\nIf you use the search bar to find this page, then select the result whose subheading is\n**Monitoring**.\n\nIf you have not yet created any services, then the **Services Overview**\nprovides a welcome message and an empty list of services:\n\nAfter you have created services, the **Services Overview** page includes the\nfollowing information:\n\n- A **Current status** summary that displays an overview of the status of\n of your services. This region is described in\n [Summary of services](/stackdriver/docs/solutions/slo-monitoring/ui/svc-overview#svc-summary).\n\n- An inventory table, **Services** , that displays information about each\n service. By default, the table shows all services, but you can filter\n the table so that it shows particular groups of services. The information\n in this table is described in [Inventory table](/stackdriver/docs/solutions/slo-monitoring/ui/svc-overview#svc-inventory).\n\n- A **Supported Services** list that classifies your defined services into\n categories. You can use this list to limit what is displayed in the\n the **Services** table. When you select a service type in the list, the\n table shows only the services of that type.\n\n### Summary of services\n\nThe summary card displays the number of services and provides information\nabout their health and configuration:\n\nThe information displayed on the summary card includes the following:\n\n- The number of services found.\n- A timestamp indicating when the summary information was collected.\n- The number of services with SLO alerts firing.\n- The number of services out of SLO budget.\n- Services with additional configuration options available.\n\nIf there are services with firing SLO alerts or exhausted error budgets, the\nsummary card displays a count and provides a **Show services** option for those\nservices. Clicking **Show services** filters the inventory table so that it\nshows only the affected services.\n\nIf there are services without defined SLOs or alerting policies, the\nsummary card describes them and provides a **Show Services** option. Clicking\n**Show Services** filters the inventory table so that it shows only those\nservices. The summary card then provides a **Learn more** option that describes\nSLOs or alerting policies.\n\nIf you have GKE entities with no associated custom services,\nthe summary card provides a **Define Service** option. For more information,\nsee [Defining a microservice](/stackdriver/docs/solutions/slo-monitoring/ui/define-svc).\n\n### Inventory table\n\nThe **Services Overview** inventory table includes a row for each service,\nas shown in the following screenshot:\n\nThe inventory table provides the following information for each service listed\nin the table:\n\n- **Name**: The display name of the service.\n\n Clicking on the name of a service brings up a dashboard for that service.\n For more information, see [Using microservice dashboards](/stackdriver/docs/solutions/slo-monitoring/ui/svc-dashboard).\n- **Type**: One of the following values:\n\n - `Istio`: an automatically detected Istio on Google Kubernetes Engine or Cloud Service Mesh service.\n - `App Engine`: an automatically detected App Engine service.\n - `Custom`: a GKE service.\n- **SLOs out of error budget**: The ratio of out-of-budget SLOs to the total\n SLO count. Services with out-of-budget SLOs are also badged to make them\n stand out in the table.\n\n- **SLOs with firing alert**: The ratio of alerting policies that are firing\n to the total count of alerting policies. Services with firing policies are\n also badged to make them stand out in the table.\n\n- **Labels**: Information about the service. The types of information\n displayed varies with the type of service.\n\n- *more_vert* **More options**: Lists changes you can make to\n the service. The choices depend on the service type:\n\n - **Edit display name**: available for all service types.\n - **Delete service**: available only for custom services.\n\nBy default, the inventory table includes all the services in your project, but\nyou can filter the table to reduce the number of entries. You can filter the\ntable from options on the summary card as described in [Summary of\nservices](/stackdriver/docs/solutions/slo-monitoring/ui/svc-overview#svc-summary), or you can filter the table directly.\n\n### Filtering the inventory table\n\nYou can filter the inventory table in the following ways:\n\n- By clicking one of the service-type entries in the\n **Supported Services** list.\n\n- By clicking one of the **Show services** options in the summary\n card, as described in [Summary of services](/stackdriver/docs/solutions/slo-monitoring/ui/svc-overview#svc-summary).\n\n- By manually adding filters to the inventory table.\n\nTo manually add a filter to the inventory table, do the following:\n\n1. Click *filter_list* **Filter**. A list of filter options is\n displayed:\n\n - **Name**: filter by SLO name.\n - **Type**: filter by SLO type.\n - **Labels**: filter by value of service labels.\n - **SLO count**: filter by number of SLOs configured.\n - **SLO alerts policies count**: filter by number of SLO-based alerting policies configured.\n2. Choose one of the options off the filter list. The chosen option appears\n in the filter bar.\n\n How you complete the filter varies with the option you select:\n 1. If you select **Type**, you then get a list of the available service\n types. Select a type from the list.\n\n 2. If you select **Name** or **Labels**, then click next to the\n text in the filter bar and start typing. Values that match are\n provided on a list. Select a value from the list.\n\n 3. If you select **SLO count** or **SLO alert policies count**, you\n then get a list of comparison operators to choose from.\n\n 1. Select an operator.\n 2. Click next to the operator and enter a comparison value.\n\n The completed filter is replaced by a filter chip. For example, the\n following chip filters for services that have 2 or fewer SLO-based\n alerting policies configured:\n\nYou can add multiple filters by repeating this process.\nAfter you add one filter, the filter-options menu also includes an `OR` option\nfor evaluating the filters. By default, services must meet a logical `AND` of\nall the filters to appear on the table.\n\nTo remove a filter, click the *close* on the filter chip.\n\nWhat's next?\n------------\n\nFor information on service-configuration tasks, see the following:\n\n- [Defining a custom service](/stackdriver/docs/solutions/slo-monitoring/ui/define-svc).\n- [Creating an SLO](/stackdriver/docs/solutions/slo-monitoring/ui/create-slo).\n- [Creating an SLO-based alerting policy](/stackdriver/docs/solutions/slo-monitoring/ui/create-alert).\n\nFor information on per-service dashboards, see [Using microservice dashboards](/stackdriver/docs/solutions/slo-monitoring/ui/svc-dashboard)."]]