Package com.google.monitoring.v3 (3.19.0)

Describes how to combine multiple time series to provide a different view of the data. Aggregation of time series is done in two steps. First, each time series in the set is aligned to the same time interval boundaries, then the set of time series is optionally reduced in number. Alignment consists of applying the per_series_aligner operation to each time series after its data has been divided into regular alignment_period time intervals. This process takes all of the data points in an alignment period, applies a mathematical transformation such as averaging, minimum, maximum, delta, etc., and converts them into a single data point per period. Reduction is when the aligned and transformed time series can optionally be combined, reducing the number of time series through similar mathematical transformations. Reduction involves applying a cross_series_reducer to all the time series, optionally sorting the time series into subsets with group_by_fields, and applying the reducer to each subset. The raw time series data can contain a huge amount of information from multiple sources. Alignment and reduction transforms this mass of data into a more manageable and representative collection of data, for example "the 95% latency across the average of all tasks in a cluster". This representative data can be more easily graphed and comprehended, and the individual time series data is still available for later drilldown. For more details, see Filtering and aggregation.

Protobuf type google.monitoring.v3.Aggregation

Describes how to combine multiple time series to provide a different view of the data. Aggregation of time series is done in two steps. First, each time series in the set is aligned to the same time interval boundaries, then the set of time series is optionally reduced in number. Alignment consists of applying the per_series_aligner operation to each time series after its data has been divided into regular alignment_period time intervals. This process takes all of the data points in an alignment period, applies a mathematical transformation such as averaging, minimum, maximum, delta, etc., and converts them into a single data point per period. Reduction is when the aligned and transformed time series can optionally be combined, reducing the number of time series through similar mathematical transformations. Reduction involves applying a cross_series_reducer to all the time series, optionally sorting the time series into subsets with group_by_fields, and applying the reducer to each subset. The raw time series data can contain a huge amount of information from multiple sources. Alignment and reduction transforms this mass of data into a more manageable and representative collection of data, for example "the 95% latency across the average of all tasks in a cluster". This representative data can be more easily graphed and comprehended, and the individual time series data is still available for later drilldown. For more details, see Filtering and aggregation.

Protobuf type google.monitoring.v3.Aggregation

A description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. For an overview of alert policies, see Introduction to Alerting.

Protobuf type google.monitoring.v3.AlertPolicy

Control over how the notification channels in notification_channels are notified when this alert fires.

Protobuf type google.monitoring.v3.AlertPolicy.AlertStrategy

Control over how the notification channels in notification_channels are notified when this alert fires.

Protobuf type google.monitoring.v3.AlertPolicy.AlertStrategy

Control over the rate of notifications sent to this alert policy's notification channels.

Protobuf type google.monitoring.v3.AlertPolicy.AlertStrategy.NotificationRateLimit

Control over the rate of notifications sent to this alert policy's notification channels.

Protobuf type google.monitoring.v3.AlertPolicy.AlertStrategy.NotificationRateLimit

A description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. For an overview of alert policies, see Introduction to Alerting.

Protobuf type google.monitoring.v3.AlertPolicy

A condition is a true/false test that determines when an alerting policy should open an incident. If a condition evaluates to true, it signifies that something is wrong.

Protobuf type google.monitoring.v3.AlertPolicy.Condition

A condition is a true/false test that determines when an alerting policy should open an incident. If a condition evaluates to true, it signifies that something is wrong.

Protobuf type google.monitoring.v3.AlertPolicy.Condition

A condition type that checks whether a log message in the scoping project satisfies the given filter. Logs from other projects in the metrics scope are not evaluated.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.LogMatch

A condition type that checks whether a log message in the scoping project satisfies the given filter. Logs from other projects in the metrics scope are not evaluated.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.LogMatch

A condition type that checks that monitored resources are reporting data. The configuration defines a metric and a set of monitored resources. The predicate is considered in violation when a time series for the specified metric of a monitored resource does not include any data in the specified duration.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.MetricAbsence

A condition type that checks that monitored resources are reporting data. The configuration defines a metric and a set of monitored resources. The predicate is considered in violation when a time series for the specified metric of a monitored resource does not include any data in the specified duration.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.MetricAbsence

A condition type that compares a collection of time series against a threshold.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.MetricThreshold

A condition type that compares a collection of time series against a threshold.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.MetricThreshold

A condition type that allows alert policies to be defined using Monitoring Query Language.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.MonitoringQueryLanguageCondition

A condition type that allows alert policies to be defined using Monitoring Query Language.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.MonitoringQueryLanguageCondition

Specifies how many time series must fail a predicate to trigger a condition. If not specified, then a {count: 1} trigger is used.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.Trigger

Specifies how many time series must fail a predicate to trigger a condition. If not specified, then a {count: 1} trigger is used.

Protobuf type google.monitoring.v3.AlertPolicy.Condition.Trigger

A content string and a MIME type that describes the content string's format.

Protobuf type google.monitoring.v3.AlertPolicy.Documentation

A content string and a MIME type that describes the content string's format.

Protobuf type google.monitoring.v3.AlertPolicy.Documentation

AUTO-GENERATED DOCUMENTATION AND CLASS

Builder for AlertPolicyConditionName.

Builder for projects/{project}/alertPolicies/{alert_policy}.

Builder for folders/{folder}/alertPolicies/{alert_policy}.

Builder for organizations/{organization}/alertPolicies/{alert_policy}.

The AlertPolicyService API is used to manage (list, create, delete, edit) alert policies in Cloud Monitoring. An alerting policy is a description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. In addition to using this API, alert policies can also be managed through Cloud Monitoring, which can be reached by clicking the "Monitoring" tab in Cloud console.

A stub to allow clients to do synchronous rpc calls to service AlertPolicyService.

The AlertPolicyService API is used to manage (list, create, delete, edit) alert policies in Cloud Monitoring. An alerting policy is a description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. In addition to using this API, alert policies can also be managed through Cloud Monitoring, which can be reached by clicking the "Monitoring" tab in Cloud console.

A stub to allow clients to do ListenableFuture-style rpc calls to service AlertPolicyService.

The AlertPolicyService API is used to manage (list, create, delete, edit) alert policies in Cloud Monitoring. An alerting policy is a description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. In addition to using this API, alert policies can also be managed through Cloud Monitoring, which can be reached by clicking the "Monitoring" tab in Cloud console.

Base class for the server implementation of the service AlertPolicyService.

The AlertPolicyService API is used to manage (list, create, delete, edit) alert policies in Cloud Monitoring. An alerting policy is a description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. In addition to using this API, alert policies can also be managed through Cloud Monitoring, which can be reached by clicking the "Monitoring" tab in Cloud console.

A stub to allow clients to do asynchronous rpc calls to service AlertPolicyService.

The AlertPolicyService API is used to manage (list, create, delete, edit) alert policies in Cloud Monitoring. An alerting policy is a description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. In addition to using this API, alert policies can also be managed through Cloud Monitoring, which can be reached by clicking the "Monitoring" tab in Cloud console.

An SLI measuring performance on a well-known service type. Performance will be computed on the basis of pre-defined metrics. The type of the service_resource determines the metrics to use and the service_resource.labels and metric_labels are used to construct a monitoring filter to filter that metric down to just the data relevant to this service.

Protobuf type google.monitoring.v3.BasicSli

Future parameters for the availability SLI.

Protobuf type google.monitoring.v3.BasicSli.AvailabilityCriteria

Future parameters for the availability SLI.

Protobuf type google.monitoring.v3.BasicSli.AvailabilityCriteria

An SLI measuring performance on a well-known service type. Performance will be computed on the basis of pre-defined metrics. The type of the service_resource determines the metrics to use and the service_resource.labels and metric_labels are used to construct a monitoring filter to filter that metric down to just the data relevant to this service.

Protobuf type google.monitoring.v3.BasicSli

Parameters for a latency threshold SLI.

Protobuf type google.monitoring.v3.BasicSli.LatencyCriteria

Parameters for a latency threshold SLI.

Protobuf type google.monitoring.v3.BasicSli.LatencyCriteria

The protocol for the CreateAlertPolicy request.

Protobuf type google.monitoring.v3.CreateAlertPolicyRequest

The protocol for the CreateAlertPolicy request.

Protobuf type google.monitoring.v3.CreateAlertPolicyRequest

The CreateGroup request.

Protobuf type google.monitoring.v3.CreateGroupRequest

The CreateGroup request.

Protobuf type google.monitoring.v3.CreateGroupRequest

The CreateMetricDescriptor request.

Protobuf type google.monitoring.v3.CreateMetricDescriptorRequest

The CreateMetricDescriptor request.

Protobuf type google.monitoring.v3.CreateMetricDescriptorRequest

The CreateNotificationChannel request.

Protobuf type google.monitoring.v3.CreateNotificationChannelRequest

The CreateNotificationChannel request.

Protobuf type google.monitoring.v3.CreateNotificationChannelRequest

The CreateServiceLevelObjective request.

Protobuf type google.monitoring.v3.CreateServiceLevelObjectiveRequest

The CreateServiceLevelObjective request.

Protobuf type google.monitoring.v3.CreateServiceLevelObjectiveRequest

The CreateService request.

Protobuf type google.monitoring.v3.CreateServiceRequest

The CreateService request.

Protobuf type google.monitoring.v3.CreateServiceRequest

The message definition for creating a Snooze. Users must provide the body of the Snooze to be created but must omit the Snooze field, name.

Protobuf type google.monitoring.v3.CreateSnoozeRequest

The message definition for creating a Snooze. Users must provide the body of the Snooze to be created but must omit the Snooze field, name.

Protobuf type google.monitoring.v3.CreateSnoozeRequest

DEPRECATED. Used to hold per-time-series error status.

Protobuf type google.monitoring.v3.CreateTimeSeriesError

DEPRECATED. Used to hold per-time-series error status.

Protobuf type google.monitoring.v3.CreateTimeSeriesError

The CreateTimeSeries request.

Protobuf type google.monitoring.v3.CreateTimeSeriesRequest

The CreateTimeSeries request.

Protobuf type google.monitoring.v3.CreateTimeSeriesRequest

Summary of the result of a failed request to write data to a time series.

Protobuf type google.monitoring.v3.CreateTimeSeriesSummary

Summary of the result of a failed request to write data to a time series.

Protobuf type google.monitoring.v3.CreateTimeSeriesSummary

Detailed information about an error category.

Protobuf type google.monitoring.v3.CreateTimeSeriesSummary.Error

Detailed information about an error category.

Protobuf type google.monitoring.v3.CreateTimeSeriesSummary.Error

The protocol for the CreateUptimeCheckConfig request.

Protobuf type google.monitoring.v3.CreateUptimeCheckConfigRequest

The protocol for the CreateUptimeCheckConfig request.

Protobuf type google.monitoring.v3.CreateUptimeCheckConfigRequest

The protocol for the DeleteAlertPolicy request.

Protobuf type google.monitoring.v3.DeleteAlertPolicyRequest

The protocol for the DeleteAlertPolicy request.

Protobuf type google.monitoring.v3.DeleteAlertPolicyRequest

The DeleteGroup request. The default behavior is to be able to delete a single group without any descendants.

Protobuf type google.monitoring.v3.DeleteGroupRequest

The DeleteGroup request. The default behavior is to be able to delete a single group without any descendants.

Protobuf type google.monitoring.v3.DeleteGroupRequest

The DeleteMetricDescriptor request.

Protobuf type google.monitoring.v3.DeleteMetricDescriptorRequest

The DeleteMetricDescriptor request.

Protobuf type google.monitoring.v3.DeleteMetricDescriptorRequest

The DeleteNotificationChannel request.

Protobuf type google.monitoring.v3.DeleteNotificationChannelRequest

The DeleteNotificationChannel request.

Protobuf type google.monitoring.v3.DeleteNotificationChannelRequest

The DeleteServiceLevelObjective request.

Protobuf type google.monitoring.v3.DeleteServiceLevelObjectiveRequest

The DeleteServiceLevelObjective request.

Protobuf type google.monitoring.v3.DeleteServiceLevelObjectiveRequest

The DeleteService request.

Protobuf type google.monitoring.v3.DeleteServiceRequest

The DeleteService request.

Protobuf type google.monitoring.v3.DeleteServiceRequest

The protocol for the DeleteUptimeCheckConfig request.

Protobuf type google.monitoring.v3.DeleteUptimeCheckConfigRequest

The protocol for the DeleteUptimeCheckConfig request.

Protobuf type google.monitoring.v3.DeleteUptimeCheckConfigRequest

A DistributionCut defines a TimeSeries and thresholds used for measuring good service and total service. The TimeSeries must have ValueType = DISTRIBUTION and MetricKind = DELTA or MetricKind = CUMULATIVE. The computed good_service will be the estimated count of values in the Distribution that fall within the specified min and max.

Protobuf type google.monitoring.v3.DistributionCut

A DistributionCut defines a TimeSeries and thresholds used for measuring good service and total service. The TimeSeries must have ValueType = DISTRIBUTION and MetricKind = DELTA or MetricKind = CUMULATIVE. The computed good_service will be the estimated count of values in the Distribution that fall within the specified min and max.

Protobuf type google.monitoring.v3.DistributionCut

A set of (label, value) pairs that were removed from a Distribution time series during aggregation and then added as an attachment to a Distribution.Exemplar. The full label set for the exemplars is constructed by using the dropped pairs in combination with the label values that remain on the aggregated Distribution time series. The constructed full label set can be used to identify the specific entity, such as the instance or job, which might be contributing to a long-tail. However, with dropped labels, the storage requirements are reduced because only the aggregated distribution values for a large group of time series are stored. Note that there are no guarantees on ordering of the labels from exemplar-to-exemplar and from distribution-to-distribution in the same stream, and there may be duplicates. It is up to clients to resolve any ambiguities.

Protobuf type google.monitoring.v3.DroppedLabels

A set of (label, value) pairs that were removed from a Distribution time series during aggregation and then added as an attachment to a Distribution.Exemplar. The full label set for the exemplars is constructed by using the dropped pairs in combination with the label values that remain on the aggregated Distribution time series. The constructed full label set can be used to identify the specific entity, such as the instance or job, which might be contributing to a long-tail. However, with dropped labels, the storage requirements are reduced because only the aggregated distribution values for a large group of time series are stored. Note that there are no guarantees on ordering of the labels from exemplar-to-exemplar and from distribution-to-distribution in the same stream, and there may be duplicates. It is up to clients to resolve any ambiguities.

Protobuf type google.monitoring.v3.DroppedLabels

Builder for folders/{folder}.

The protocol for the GetAlertPolicy request.

Protobuf type google.monitoring.v3.GetAlertPolicyRequest

The protocol for the GetAlertPolicy request.

Protobuf type google.monitoring.v3.GetAlertPolicyRequest

The GetGroup request.

Protobuf type google.monitoring.v3.GetGroupRequest

The GetGroup request.

Protobuf type google.monitoring.v3.GetGroupRequest

The GetMetricDescriptor request.

Protobuf type google.monitoring.v3.GetMetricDescriptorRequest

The GetMetricDescriptor request.

Protobuf type google.monitoring.v3.GetMetricDescriptorRequest

The GetMonitoredResourceDescriptor request.

Protobuf type google.monitoring.v3.GetMonitoredResourceDescriptorRequest

The GetMonitoredResourceDescriptor request.

Protobuf type google.monitoring.v3.GetMonitoredResourceDescriptorRequest

The GetNotificationChannelDescriptor response.

Protobuf type google.monitoring.v3.GetNotificationChannelDescriptorRequest

The GetNotificationChannelDescriptor response.

Protobuf type google.monitoring.v3.GetNotificationChannelDescriptorRequest

The GetNotificationChannel request.

Protobuf type google.monitoring.v3.GetNotificationChannelRequest

The GetNotificationChannel request.

Protobuf type google.monitoring.v3.GetNotificationChannelRequest

The GetNotificationChannelVerificationCode request.

Protobuf type google.monitoring.v3.GetNotificationChannelVerificationCodeRequest

The GetNotificationChannelVerificationCode request.

Protobuf type google.monitoring.v3.GetNotificationChannelVerificationCodeRequest

The GetNotificationChannelVerificationCode request.

Protobuf type google.monitoring.v3.GetNotificationChannelVerificationCodeResponse

The GetNotificationChannelVerificationCode request.

Protobuf type google.monitoring.v3.GetNotificationChannelVerificationCodeResponse

The GetServiceLevelObjective request.

Protobuf type google.monitoring.v3.GetServiceLevelObjectiveRequest

The GetServiceLevelObjective request.

Protobuf type google.monitoring.v3.GetServiceLevelObjectiveRequest

The GetService request.

Protobuf type google.monitoring.v3.GetServiceRequest

The GetService request.

Protobuf type google.monitoring.v3.GetServiceRequest

The message definition for retrieving a Snooze. Users must specify the field, name, which identifies the Snooze.

Protobuf type google.monitoring.v3.GetSnoozeRequest

The message definition for retrieving a Snooze. Users must specify the field, name, which identifies the Snooze.

Protobuf type google.monitoring.v3.GetSnoozeRequest

The protocol for the GetUptimeCheckConfig request.

Protobuf type google.monitoring.v3.GetUptimeCheckConfigRequest

The protocol for the GetUptimeCheckConfig request.

Protobuf type google.monitoring.v3.GetUptimeCheckConfigRequest

The description of a dynamic collection of monitored resources. Each group has a filter that is matched against monitored resources and their associated metadata. If a group's filter matches an available monitored resource, then that resource is a member of that group. Groups can contain any number of monitored resources, and each monitored resource can be a member of any number of groups. Groups can be nested in parent-child hierarchies. The parentName field identifies an optional parent for each group. If a group has a parent, then the only monitored resources available to be matched by the group's filter are the resources contained in the parent group. In other words, a group contains the monitored resources that match its filter and the filters of all the group's ancestors. A group without a parent can contain any monitored resource. For example, consider an infrastructure running a set of instances with two user-defined tags: "environment" and "role". A parent group has a filter, environment="production". A child of that parent group has a filter, role="transcoder". The parent group contains all instances in the production environment, regardless of their roles. The child group contains instances that have the transcoder role and are in the production environment. The monitored resources contained in a group can change at any moment, depending on what resources exist and what filters are associated with the group and its ancestors.

Protobuf type google.monitoring.v3.Group

The description of a dynamic collection of monitored resources. Each group has a filter that is matched against monitored resources and their associated metadata. If a group's filter matches an available monitored resource, then that resource is a member of that group. Groups can contain any number of monitored resources, and each monitored resource can be a member of any number of groups. Groups can be nested in parent-child hierarchies. The parentName field identifies an optional parent for each group. If a group has a parent, then the only monitored resources available to be matched by the group's filter are the resources contained in the parent group. In other words, a group contains the monitored resources that match its filter and the filters of all the group's ancestors. A group without a parent can contain any monitored resource. For example, consider an infrastructure running a set of instances with two user-defined tags: "environment" and "role". A parent group has a filter, environment="production". A child of that parent group has a filter, role="transcoder". The parent group contains all instances in the production environment, regardless of their roles. The child group contains instances that have the transcoder role and are in the production environment. The monitored resources contained in a group can change at any moment, depending on what resources exist and what filters are associated with the group and its ancestors.

Protobuf type google.monitoring.v3.Group

Builder for projects/{project}/groups/{group}.

Builder for folders/{folder}/groups/{group}.

Builder for organizations/{organization}/groups/{group}.

The Group API lets you inspect and manage your groups. A group is a named filter that is used to identify a collection of monitored resources. Groups are typically used to mirror the physical and/or logical topology of the environment. Because group membership is computed dynamically, monitored resources that are started in the future are automatically placed in matching groups. By using a group to name monitored resources in, for example, an alert policy, the target of that alert policy is updated automatically as monitored resources are added and removed from the infrastructure.

A stub to allow clients to do synchronous rpc calls to service GroupService.

The Group API lets you inspect and manage your groups. A group is a named filter that is used to identify a collection of monitored resources. Groups are typically used to mirror the physical and/or logical topology of the environment. Because group membership is computed dynamically, monitored resources that are started in the future are automatically placed in matching groups. By using a group to name monitored resources in, for example, an alert policy, the target of that alert policy is updated automatically as monitored resources are added and removed from the infrastructure.

A stub to allow clients to do ListenableFuture-style rpc calls to service GroupService.

The Group API lets you inspect and manage your groups. A group is a named filter that is used to identify a collection of monitored resources. Groups are typically used to mirror the physical and/or logical topology of the environment. Because group membership is computed dynamically, monitored resources that are started in the future are automatically placed in matching groups. By using a group to name monitored resources in, for example, an alert policy, the target of that alert policy is updated automatically as monitored resources are added and removed from the infrastructure.

Base class for the server implementation of the service GroupService.

The Group API lets you inspect and manage your groups. A group is a named filter that is used to identify a collection of monitored resources. Groups are typically used to mirror the physical and/or logical topology of the environment. Because group membership is computed dynamically, monitored resources that are started in the future are automatically placed in matching groups. By using a group to name monitored resources in, for example, an alert policy, the target of that alert policy is updated automatically as monitored resources are added and removed from the infrastructure.

A stub to allow clients to do asynchronous rpc calls to service GroupService.

The Group API lets you inspect and manage your groups. A group is a named filter that is used to identify a collection of monitored resources. Groups are typically used to mirror the physical and/or logical topology of the environment. Because group membership is computed dynamically, monitored resources that are started in the future are automatically placed in matching groups. By using a group to name monitored resources in, for example, an alert policy, the target of that alert policy is updated automatically as monitored resources are added and removed from the infrastructure.

An internal checker allows Uptime checks to run on private/internal GCP resources.

Protobuf type google.monitoring.v3.InternalChecker

An internal checker allows Uptime checks to run on private/internal GCP resources.

Protobuf type google.monitoring.v3.InternalChecker

A label value.

Protobuf type google.monitoring.v3.LabelValue

A label value.

Protobuf type google.monitoring.v3.LabelValue

The protocol for the ListAlertPolicies request.

Protobuf type google.monitoring.v3.ListAlertPoliciesRequest

The protocol for the ListAlertPolicies request.

Protobuf type google.monitoring.v3.ListAlertPoliciesRequest

The protocol for the ListAlertPolicies response.

Protobuf type google.monitoring.v3.ListAlertPoliciesResponse

The protocol for the ListAlertPolicies response.

Protobuf type google.monitoring.v3.ListAlertPoliciesResponse

The ListGroupMembers request.

Protobuf type google.monitoring.v3.ListGroupMembersRequest

The ListGroupMembers request.

Protobuf type google.monitoring.v3.ListGroupMembersRequest

The ListGroupMembers response.

Protobuf type google.monitoring.v3.ListGroupMembersResponse

The ListGroupMembers response.

Protobuf type google.monitoring.v3.ListGroupMembersResponse

The ListGroup request.

Protobuf type google.monitoring.v3.ListGroupsRequest

The ListGroup request.

Protobuf type google.monitoring.v3.ListGroupsRequest

The ListGroups response.

Protobuf type google.monitoring.v3.ListGroupsResponse

The ListGroups response.

Protobuf type google.monitoring.v3.ListGroupsResponse

The ListMetricDescriptors request.

Protobuf type google.monitoring.v3.ListMetricDescriptorsRequest

The ListMetricDescriptors request.

Protobuf type google.monitoring.v3.ListMetricDescriptorsRequest

The ListMetricDescriptors response.

Protobuf type google.monitoring.v3.ListMetricDescriptorsResponse

The ListMetricDescriptors response.

Protobuf type google.monitoring.v3.ListMetricDescriptorsResponse

The ListMonitoredResourceDescriptors request.

Protobuf type google.monitoring.v3.ListMonitoredResourceDescriptorsRequest

The ListMonitoredResourceDescriptors request.

Protobuf type google.monitoring.v3.ListMonitoredResourceDescriptorsRequest

The ListMonitoredResourceDescriptors response.

Protobuf type google.monitoring.v3.ListMonitoredResourceDescriptorsResponse

The ListMonitoredResourceDescriptors response.

Protobuf type google.monitoring.v3.ListMonitoredResourceDescriptorsResponse

The ListNotificationChannelDescriptors request.

Protobuf type google.monitoring.v3.ListNotificationChannelDescriptorsRequest

The ListNotificationChannelDescriptors request.

Protobuf type google.monitoring.v3.ListNotificationChannelDescriptorsRequest

The ListNotificationChannelDescriptors response.

Protobuf type google.monitoring.v3.ListNotificationChannelDescriptorsResponse

The ListNotificationChannelDescriptors response.

Protobuf type google.monitoring.v3.ListNotificationChannelDescriptorsResponse

The ListNotificationChannels request.

Protobuf type google.monitoring.v3.ListNotificationChannelsRequest

The ListNotificationChannels request.

Protobuf type google.monitoring.v3.ListNotificationChannelsRequest

The ListNotificationChannels response.

Protobuf type google.monitoring.v3.ListNotificationChannelsResponse

The ListNotificationChannels response.

Protobuf type google.monitoring.v3.ListNotificationChannelsResponse

The ListServiceLevelObjectives request.

Protobuf type google.monitoring.v3.ListServiceLevelObjectivesRequest

The ListServiceLevelObjectives request.

Protobuf type google.monitoring.v3.ListServiceLevelObjectivesRequest

The ListServiceLevelObjectives response.

Protobuf type google.monitoring.v3.ListServiceLevelObjectivesResponse

The ListServiceLevelObjectives response.

Protobuf type google.monitoring.v3.ListServiceLevelObjectivesResponse

The ListServices request.

Protobuf type google.monitoring.v3.ListServicesRequest

The ListServices request.

Protobuf type google.monitoring.v3.ListServicesRequest

The ListServices response.

Protobuf type google.monitoring.v3.ListServicesResponse

The ListServices response.

Protobuf type google.monitoring.v3.ListServicesResponse

The message definition for listing Snoozes associated with the given parent, satisfying the optional filter.

Protobuf type google.monitoring.v3.ListSnoozesRequest

The message definition for listing Snoozes associated with the given parent, satisfying the optional filter.

Protobuf type google.monitoring.v3.ListSnoozesRequest

The results of a successful ListSnoozes call, containing the matching Snoozes.

Protobuf type google.monitoring.v3.ListSnoozesResponse

The results of a successful ListSnoozes call, containing the matching Snoozes.

Protobuf type google.monitoring.v3.ListSnoozesResponse

The ListTimeSeries request.

Protobuf type google.monitoring.v3.ListTimeSeriesRequest

The ListTimeSeries request.

Protobuf type google.monitoring.v3.ListTimeSeriesRequest

The ListTimeSeries response.

Protobuf type google.monitoring.v3.ListTimeSeriesResponse

The ListTimeSeries response.

Protobuf type google.monitoring.v3.ListTimeSeriesResponse

The protocol for the ListUptimeCheckConfigs request.

Protobuf type google.monitoring.v3.ListUptimeCheckConfigsRequest

The protocol for the ListUptimeCheckConfigs request.

Protobuf type google.monitoring.v3.ListUptimeCheckConfigsRequest

The protocol for the ListUptimeCheckConfigs response.

Protobuf type google.monitoring.v3.ListUptimeCheckConfigsResponse

The protocol for the ListUptimeCheckConfigs response.

Protobuf type google.monitoring.v3.ListUptimeCheckConfigsResponse

The protocol for the ListUptimeCheckIps request.

Protobuf type google.monitoring.v3.ListUptimeCheckIpsRequest

The protocol for the ListUptimeCheckIps request.

Protobuf type google.monitoring.v3.ListUptimeCheckIpsRequest

The protocol for the ListUptimeCheckIps response.

Protobuf type google.monitoring.v3.ListUptimeCheckIpsResponse

The protocol for the ListUptimeCheckIps response.

Protobuf type google.monitoring.v3.ListUptimeCheckIpsResponse

Builder for projects/{project}/metricDescriptors/{metric_descriptor=**}.

Builder for folders/{folder}/metricDescriptors/{metric_descriptor=**}.

Builder for organizations/{organization}/metricDescriptors/{metric_descriptor=**}.

Manages metric descriptors, monitored resource descriptors, and time series data.

A stub to allow clients to do synchronous rpc calls to service MetricService.

Manages metric descriptors, monitored resource descriptors, and time series data.

A stub to allow clients to do ListenableFuture-style rpc calls to service MetricService.

Manages metric descriptors, monitored resource descriptors, and time series data.

Base class for the server implementation of the service MetricService.

Manages metric descriptors, monitored resource descriptors, and time series data.

A stub to allow clients to do asynchronous rpc calls to service MetricService.

Manages metric descriptors, monitored resource descriptors, and time series data.

Builder for projects/{project}/monitoredResourceDescriptors/{monitored_resource_descriptor}.

Builder for folders/{folder}/monitoredResourceDescriptors/{monitored_resource_descriptor}.

Builder for organizations/{organization}/monitoredResourceDescriptors/{monitored_resource_descriptor}.

Describes a change made to a configuration.

Protobuf type google.monitoring.v3.MutationRecord

Describes a change made to a configuration.

Protobuf type google.monitoring.v3.MutationRecord

A NotificationChannel is a medium through which an alert is delivered when a policy violation is detected. Examples of channels include email, SMS, and third-party messaging applications. Fields containing sensitive information like authentication tokens or contact info are only partially populated on retrieval.

Protobuf type google.monitoring.v3.NotificationChannel

A NotificationChannel is a medium through which an alert is delivered when a policy violation is detected. Examples of channels include email, SMS, and third-party messaging applications. Fields containing sensitive information like authentication tokens or contact info are only partially populated on retrieval.

Protobuf type google.monitoring.v3.NotificationChannel

A description of a notification channel. The descriptor includes the properties of the channel and the set of labels or fields that must be specified to configure channels of a given type.

Protobuf type google.monitoring.v3.NotificationChannelDescriptor

A description of a notification channel. The descriptor includes the properties of the channel and the set of labels or fields that must be specified to configure channels of a given type.

Protobuf type google.monitoring.v3.NotificationChannelDescriptor

Builder for projects/{project}/notificationChannelDescriptors/{channel_descriptor}.

Builder for folders/{folder}/notificationChannelDescriptors/{channel_descriptor}.

Builder for organizations/{organization}/notificationChannelDescriptors/{channel_descriptor}.

Builder for projects/{project}/notificationChannels/{notification_channel}.

Builder for folders/{folder}/notificationChannels/{notification_channel}.

Builder for organizations/{organization}/notificationChannels/{notification_channel}.

The Notification Channel API provides access to configuration that controls how messages related to incidents are sent.

A stub to allow clients to do synchronous rpc calls to service NotificationChannelService.

The Notification Channel API provides access to configuration that controls how messages related to incidents are sent.

A stub to allow clients to do ListenableFuture-style rpc calls to service NotificationChannelService.

The Notification Channel API provides access to configuration that controls how messages related to incidents are sent.

Base class for the server implementation of the service NotificationChannelService.

The Notification Channel API provides access to configuration that controls how messages related to incidents are sent.

A stub to allow clients to do asynchronous rpc calls to service NotificationChannelService.

The Notification Channel API provides access to configuration that controls how messages related to incidents are sent.

Builder for organizations/{organization}.

A single data point in a time series.

Protobuf type google.monitoring.v3.Point

A single data point in a time series.

Protobuf type google.monitoring.v3.Point

Builder for projects/{project}.

An error associated with a query in the time series query language format.

Protobuf type google.monitoring.v3.QueryError

An error associated with a query in the time series query language format.

Protobuf type google.monitoring.v3.QueryError

This is an error detail intended to be used with INVALID_ARGUMENT errors.

Protobuf type google.monitoring.v3.QueryErrorList

This is an error detail intended to be used with INVALID_ARGUMENT errors.

Protobuf type google.monitoring.v3.QueryErrorList

The QueryService API is used to manage time series data in Stackdriver Monitoring. Time series data is a collection of data points that describes the time-varying values of a metric.

A stub to allow clients to do synchronous rpc calls to service QueryService.

The QueryService API is used to manage time series data in Stackdriver Monitoring. Time series data is a collection of data points that describes the time-varying values of a metric.

A stub to allow clients to do ListenableFuture-style rpc calls to service QueryService.

The QueryService API is used to manage time series data in Stackdriver Monitoring. Time series data is a collection of data points that describes the time-varying values of a metric.

Base class for the server implementation of the service QueryService.

The QueryService API is used to manage time series data in Stackdriver Monitoring. Time series data is a collection of data points that describes the time-varying values of a metric.

A stub to allow clients to do asynchronous rpc calls to service QueryService.

The QueryService API is used to manage time series data in Stackdriver Monitoring. Time series data is a collection of data points that describes the time-varying values of a metric.

The QueryTimeSeries request.

Protobuf type google.monitoring.v3.QueryTimeSeriesRequest

The QueryTimeSeries request.

Protobuf type google.monitoring.v3.QueryTimeSeriesRequest

The QueryTimeSeries response.

Protobuf type google.monitoring.v3.QueryTimeSeriesResponse

The QueryTimeSeries response.

Protobuf type google.monitoring.v3.QueryTimeSeriesResponse

Range of numerical values within min and max.

Protobuf type google.monitoring.v3.Range

Range of numerical values within min and max.

Protobuf type google.monitoring.v3.Range

Service Level Indicators for which atomic units of service are counted directly.

Protobuf type google.monitoring.v3.RequestBasedSli

Service Level Indicators for which atomic units of service are counted directly.

Protobuf type google.monitoring.v3.RequestBasedSli

The SendNotificationChannelVerificationCode request.

Protobuf type google.monitoring.v3.SendNotificationChannelVerificationCodeRequest

The SendNotificationChannelVerificationCode request.

Protobuf type google.monitoring.v3.SendNotificationChannelVerificationCodeRequest

A Service is a discrete, autonomous, and network-accessible unit, designed to solve an individual concern (Wikipedia). In Cloud Monitoring, a Service acts as the root resource under which operational aspects of the service are accessible.

Protobuf type google.monitoring.v3.Service

App Engine service. Learn more at https://cloud.google.com/appengine.

Protobuf type google.monitoring.v3.Service.AppEngine

App Engine service. Learn more at https://cloud.google.com/appengine.

Protobuf type google.monitoring.v3.Service.AppEngine

A Service is a discrete, autonomous, and network-accessible unit, designed to solve an individual concern (Wikipedia). In Cloud Monitoring, a Service acts as the root resource under which operational aspects of the service are accessible.

Protobuf type google.monitoring.v3.Service

Cloud Endpoints service. Learn more at https://cloud.google.com/endpoints.

Protobuf type google.monitoring.v3.Service.CloudEndpoints

Cloud Endpoints service. Learn more at https://cloud.google.com/endpoints.

Protobuf type google.monitoring.v3.Service.CloudEndpoints

Istio service scoped to a single Kubernetes cluster. Learn more at https://istio.io. Clusters running OSS Istio will have their services ingested as this type.

Protobuf type google.monitoring.v3.Service.ClusterIstio

Istio service scoped to a single Kubernetes cluster. Learn more at https://istio.io. Clusters running OSS Istio will have their services ingested as this type.

Protobuf type google.monitoring.v3.Service.ClusterIstio

Custom view of service telemetry. Currently a place-holder pending final design.

Protobuf type google.monitoring.v3.Service.Custom

Custom view of service telemetry. Currently a place-holder pending final design.

Protobuf type google.monitoring.v3.Service.Custom

Canonical service scoped to an Istio mesh. Anthos clusters running ASM >= 1.6.8 will have their services ingested as this type.

Protobuf type google.monitoring.v3.Service.IstioCanonicalService

Canonical service scoped to an Istio mesh. Anthos clusters running ASM >= 1.6.8 will have their services ingested as this type.

Protobuf type google.monitoring.v3.Service.IstioCanonicalService

Istio service scoped to an Istio mesh. Anthos clusters running ASM < 1.6.8 will have their services ingested as this type.

Protobuf type google.monitoring.v3.Service.MeshIstio

Istio service scoped to an Istio mesh. Anthos clusters running ASM < 1.6.8 will have their services ingested as this type.

Protobuf type google.monitoring.v3.Service.MeshIstio

Configuration for how to query telemetry on a Service.

Protobuf type google.monitoring.v3.Service.Telemetry

Configuration for how to query telemetry on a Service.

Protobuf type google.monitoring.v3.Service.Telemetry

A Service-Level Indicator (SLI) describes the "performance" of a service. For some services, the SLI is well-defined. In such cases, the SLI can be described easily by referencing the well-known SLI and providing the needed parameters. Alternatively, a "custom" SLI can be defined with a query to the underlying metric store. An SLI is defined to be good_service / total_service over any queried time interval. The value of performance always falls into the range 0 <= performance <= 1. A custom SLI describes how to compute this ratio, whether this is by dividing values from a pair of time series, cutting a Distribution into good and bad counts, or counting time windows in which the service complies with a criterion. For separation of concerns, a single Service-Level Indicator measures performance for only one aspect of service quality, such as fraction of successful queries or fast-enough queries.

Protobuf type google.monitoring.v3.ServiceLevelIndicator

A Service-Level Indicator (SLI) describes the "performance" of a service. For some services, the SLI is well-defined. In such cases, the SLI can be described easily by referencing the well-known SLI and providing the needed parameters. Alternatively, a "custom" SLI can be defined with a query to the underlying metric store. An SLI is defined to be good_service / total_service over any queried time interval. The value of performance always falls into the range 0 <= performance <= 1. A custom SLI describes how to compute this ratio, whether this is by dividing values from a pair of time series, cutting a Distribution into good and bad counts, or counting time windows in which the service complies with a criterion. For separation of concerns, a single Service-Level Indicator measures performance for only one aspect of service quality, such as fraction of successful queries or fast-enough queries.

Protobuf type google.monitoring.v3.ServiceLevelIndicator

A Service-Level Objective (SLO) describes a level of desired good service. It consists of a service-level indicator (SLI), a performance goal, and a period over which the objective is to be evaluated against that goal. The SLO can use SLIs defined in a number of different manners. Typical SLOs might include "99% of requests in each rolling week have latency below 200 milliseconds" or "99.5% of requests in each calendar month return successfully."

Protobuf type google.monitoring.v3.ServiceLevelObjective

A Service-Level Objective (SLO) describes a level of desired good service. It consists of a service-level indicator (SLI), a performance goal, and a period over which the objective is to be evaluated against that goal. The SLO can use SLIs defined in a number of different manners. Typical SLOs might include "99% of requests in each rolling week have latency below 200 milliseconds" or "99.5% of requests in each calendar month return successfully."

Protobuf type google.monitoring.v3.ServiceLevelObjective

Builder for projects/{project}/services/{service}/serviceLevelObjectives/{service_level_objective}.

Builder for folders/{folder}/services/{service}/serviceLevelObjectives/{service_level_objective}.

Builder for organizations/{organization}/services/{service}/serviceLevelObjectives/{service_level_objective}.

The Cloud Monitoring Service-Oriented Monitoring API has endpoints for managing and querying aspects of a workspace's services. These include the Service's monitored resources, its Service-Level Objectives, and a taxonomy of categorized Health Metrics.

A stub to allow clients to do synchronous rpc calls to service ServiceMonitoringService.

The Cloud Monitoring Service-Oriented Monitoring API has endpoints for managing and querying aspects of a workspace's services. These include the Service's monitored resources, its Service-Level Objectives, and a taxonomy of categorized Health Metrics.

A stub to allow clients to do ListenableFuture-style rpc calls to service ServiceMonitoringService.

The Cloud Monitoring Service-Oriented Monitoring API has endpoints for managing and querying aspects of a workspace's services. These include the Service's monitored resources, its Service-Level Objectives, and a taxonomy of categorized Health Metrics.

Base class for the server implementation of the service ServiceMonitoringService.

The Cloud Monitoring Service-Oriented Monitoring API has endpoints for managing and querying aspects of a workspace's services. These include the Service's monitored resources, its Service-Level Objectives, and a taxonomy of categorized Health Metrics.

A stub to allow clients to do asynchronous rpc calls to service ServiceMonitoringService.

The Cloud Monitoring Service-Oriented Monitoring API has endpoints for managing and querying aspects of a workspace's services. These include the Service's monitored resources, its Service-Level Objectives, and a taxonomy of categorized Health Metrics.

Builder for projects/{project}/services/{service}.

Builder for folders/{folder}/services/{service}.

Builder for organizations/{organization}/services/{service}.

A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.

Protobuf type google.monitoring.v3.Snooze

A Snooze will prevent any alerts from being opened, and close any that are already open. The Snooze will work on alerts that match the criteria defined in the Snooze. The Snooze will be active from interval.start_time through interval.end_time.

Protobuf type google.monitoring.v3.Snooze

Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied.

Protobuf type google.monitoring.v3.Snooze.Criteria

Criteria specific to the AlertPolicys that this Snooze applies to. The Snooze will suppress alerts that come from one of the AlertPolicys whose names are supplied.

Protobuf type google.monitoring.v3.Snooze.Criteria

Builder for projects/{project}/snoozes/{snooze}.

The SnoozeService API is used to temporarily prevent an alert policy from generating alerts. A Snooze is a description of the criteria under which one or more alert policies should not fire alerts for the specified duration.

A stub to allow clients to do synchronous rpc calls to service SnoozeService.

The SnoozeService API is used to temporarily prevent an alert policy from generating alerts. A Snooze is a description of the criteria under which one or more alert policies should not fire alerts for the specified duration.

A stub to allow clients to do ListenableFuture-style rpc calls to service SnoozeService.

The SnoozeService API is used to temporarily prevent an alert policy from generating alerts. A Snooze is a description of the criteria under which one or more alert policies should not fire alerts for the specified duration.

Base class for the server implementation of the service SnoozeService.

The SnoozeService API is used to temporarily prevent an alert policy from generating alerts. A Snooze is a description of the criteria under which one or more alert policies should not fire alerts for the specified duration.

A stub to allow clients to do asynchronous rpc calls to service SnoozeService.

The SnoozeService API is used to temporarily prevent an alert policy from generating alerts. A Snooze is a description of the criteria under which one or more alert policies should not fire alerts for the specified duration.

The context of a span. This is attached to an Exemplar in Distribution values during aggregation. It contains the name of a span with format: projects/[PROJECT_ID_OR_NUMBER]/traces/[TRACE_ID]/spans/[SPAN_ID]

Protobuf type google.monitoring.v3.SpanContext

The context of a span. This is attached to an Exemplar in Distribution values during aggregation. It contains the name of a span with format: projects/[PROJECT_ID_OR_NUMBER]/traces/[TRACE_ID]/spans/[SPAN_ID]

Protobuf type google.monitoring.v3.SpanContext

A locator for text. Indicates a particular part of the text of a request or of an object referenced in the request. For example, suppose the request field text contains: text: "The quick brown fox jumps over the lazy dog." Then the locator: source: "text" start_position { line: 1 column: 17 } end_position { line: 1 column: 19 } refers to the part of the text: "fox".

Protobuf type google.monitoring.v3.TextLocator

A locator for text. Indicates a particular part of the text of a request or of an object referenced in the request. For example, suppose the request field text contains: text: "The quick brown fox jumps over the lazy dog." Then the locator: source: "text" start_position { line: 1 column: 17 } end_position { line: 1 column: 19 } refers to the part of the text: "fox".

Protobuf type google.monitoring.v3.TextLocator

The position of a byte within the text.

Protobuf type google.monitoring.v3.TextLocator.Position

The position of a byte within the text.

Protobuf type google.monitoring.v3.TextLocator.Position

A closed time interval. It extends from the start time to the end time, and includes both: [startTime, endTime]. Valid time intervals depend on the MetricKind of the metric value. The end time must not be earlier than the start time. When writing data points, the start time must not be more than 25 hours in the past and the end time must not be more than five minutes in the future.

• For GAUGE metrics, the startTime value is technically optional; if no value is specified, the start time defaults to the value of the end time, and the interval represents a single point in time. If both start and end times are specified, they must be identical. Such an interval is valid only for GAUGE metrics, which are point-in-time measurements. The end time of a new interval must be at least a millisecond after the end time of the previous interval.
• For DELTA metrics, the start time and end time must specify a non-zero interval, with subsequent points specifying contiguous and non-overlapping intervals. For DELTA metrics, the start time of the next interval must be at least a millisecond after the end time of the previous interval.
• For CUMULATIVE metrics, the start time and end time must specify a non-zero interval, with subsequent points specifying the same start time and increasing end times, until an event resets the cumulative value to zero and sets a new start time for the following points. The new start time must be at least a millisecond after the end time of the previous interval.
• The start time of a new interval must be at least a millisecond after the end time of the previous interval because intervals are closed. If the start time of a new interval is the same as the end time of the previous interval, then data written at the new start time could overwrite data written at the previous end time.

Protobuf type google.monitoring.v3.TimeInterval

A closed time interval. It extends from the start time to the end time, and includes both: [startTime, endTime]. Valid time intervals depend on the MetricKind of the metric value. The end time must not be earlier than the start time. When writing data points, the start time must not be more than 25 hours in the past and the end time must not be more than five minutes in the future.

• For GAUGE metrics, the startTime value is technically optional; if no value is specified, the start time defaults to the value of the end time, and the interval represents a single point in time. If both start and end times are specified, they must be identical. Such an interval is valid only for GAUGE metrics, which are point-in-time measurements. The end time of a new interval must be at least a millisecond after the end time of the previous interval.
• For DELTA metrics, the start time and end time must specify a non-zero interval, with subsequent points specifying contiguous and non-overlapping intervals. For DELTA metrics, the start time of the next interval must be at least a millisecond after the end time of the previous interval.
• For CUMULATIVE metrics, the start time and end time must specify a non-zero interval, with subsequent points specifying the same start time and increasing end times, until an event resets the cumulative value to zero and sets a new start time for the following points. The new start time must be at least a millisecond after the end time of the previous interval.
• The start time of a new interval must be at least a millisecond after the end time of the previous interval because intervals are closed. If the start time of a new interval is the same as the end time of the previous interval, then data written at the new start time could overwrite data written at the previous end time.

Protobuf type google.monitoring.v3.TimeInterval

A collection of data points that describes the time-varying values of a metric. A time series is identified by a combination of a fully-specified monitored resource and a fully-specified metric. This type is used for both listing and creating time series.

Protobuf type google.monitoring.v3.TimeSeries

A collection of data points that describes the time-varying values of a metric. A time series is identified by a combination of a fully-specified monitored resource and a fully-specified metric. This type is used for both listing and creating time series.

Protobuf type google.monitoring.v3.TimeSeries

Represents the values of a time series associated with a TimeSeriesDescriptor.

Protobuf type google.monitoring.v3.TimeSeriesData

Represents the values of a time series associated with a TimeSeriesDescriptor.

Protobuf type google.monitoring.v3.TimeSeriesData

A point's value columns and time interval. Each point has one or more point values corresponding to the entries in point_descriptors field in the TimeSeriesDescriptor associated with this object.

Protobuf type google.monitoring.v3.TimeSeriesData.PointData

A point's value columns and time interval. Each point has one or more point values corresponding to the entries in point_descriptors field in the TimeSeriesDescriptor associated with this object.

Protobuf type google.monitoring.v3.TimeSeriesData.PointData

A descriptor for the labels and points in a time series.

Protobuf type google.monitoring.v3.TimeSeriesDescriptor

A descriptor for the labels and points in a time series.

Protobuf type google.monitoring.v3.TimeSeriesDescriptor

A descriptor for the value columns in a data point.

Protobuf type google.monitoring.v3.TimeSeriesDescriptor.ValueDescriptor

A descriptor for the value columns in a data point.

Protobuf type google.monitoring.v3.TimeSeriesDescriptor.ValueDescriptor

Builder for projects/{project}/timeSeries/{time_series}.

Builder for folders/{folder}/timeSeries/{time_series}.

Builder for organizations/{organization}/timeSeries/{time_series}.

A TimeSeriesRatio specifies two TimeSeries to use for computing the good_service / total_service ratio. The specified TimeSeries must have ValueType = DOUBLE or ValueType = INT64 and must have MetricKind = DELTA or MetricKind = CUMULATIVE. The TimeSeriesRatio must specify exactly two of good, bad, and total, and the relationship good_service + bad_service = total_service will be assumed.

Protobuf type google.monitoring.v3.TimeSeriesRatio

A TimeSeriesRatio specifies two TimeSeries to use for computing the good_service / total_service ratio. The specified TimeSeries must have ValueType = DOUBLE or ValueType = INT64 and must have MetricKind = DELTA or MetricKind = CUMULATIVE. The TimeSeriesRatio must specify exactly two of good, bad, and total, and the relationship good_service + bad_service = total_service will be assumed.

Protobuf type google.monitoring.v3.TimeSeriesRatio

A single strongly-typed value.

Protobuf type google.monitoring.v3.TypedValue

A single strongly-typed value.

Protobuf type google.monitoring.v3.TypedValue

The protocol for the UpdateAlertPolicy request.

Protobuf type google.monitoring.v3.UpdateAlertPolicyRequest

The protocol for the UpdateAlertPolicy request.

Protobuf type google.monitoring.v3.UpdateAlertPolicyRequest

The UpdateGroup request.

Protobuf type google.monitoring.v3.UpdateGroupRequest

The UpdateGroup request.

Protobuf type google.monitoring.v3.UpdateGroupRequest

The UpdateNotificationChannel request.

Protobuf type google.monitoring.v3.UpdateNotificationChannelRequest

The UpdateNotificationChannel request.

Protobuf type google.monitoring.v3.UpdateNotificationChannelRequest

The UpdateServiceLevelObjective request.

Protobuf type google.monitoring.v3.UpdateServiceLevelObjectiveRequest

The UpdateServiceLevelObjective request.

Protobuf type google.monitoring.v3.UpdateServiceLevelObjectiveRequest

The UpdateService request.

Protobuf type google.monitoring.v3.UpdateServiceRequest

The UpdateService request.

Protobuf type google.monitoring.v3.UpdateServiceRequest

The message definition for updating a Snooze. The field, snooze.name identifies the Snooze to be updated. The remainder of snooze gives the content the Snooze in question will be assigned. What fields can be updated depends on the start time and end time of the Snooze.

• end time is in the past: These Snoozes are considered read-only and cannot be updated.
• start time is in the past and end time is in the future: display_name and interval.end_time can be updated.
• start time is in the future: display_name, interval.start_time and interval.end_time can be updated.

Protobuf type google.monitoring.v3.UpdateSnoozeRequest

The message definition for updating a Snooze. The field, snooze.name identifies the Snooze to be updated. The remainder of snooze gives the content the Snooze in question will be assigned. What fields can be updated depends on the start time and end time of the Snooze.

• end time is in the past: These Snoozes are considered read-only and cannot be updated.
• start time is in the past and end time is in the future: display_name and interval.end_time can be updated.
• start time is in the future: display_name, interval.start_time and interval.end_time can be updated.

Protobuf type google.monitoring.v3.UpdateSnoozeRequest

The protocol for the UpdateUptimeCheckConfig request.

Protobuf type google.monitoring.v3.UpdateUptimeCheckConfigRequest

The protocol for the UpdateUptimeCheckConfig request.

Protobuf type google.monitoring.v3.UpdateUptimeCheckConfigRequest

This message configures which resources and services to monitor for availability.

Protobuf type google.monitoring.v3.UptimeCheckConfig

This message configures which resources and services to monitor for availability.

Protobuf type google.monitoring.v3.UptimeCheckConfig

Optional. Used to perform content matching. This allows matching based on substrings and regular expressions, together with their negations. Only the first 4&nbsp;MB of an HTTP or HTTPS check's response (and the first 1&nbsp;MB of a TCP check's response) are examined for purposes of content matching.

Protobuf type google.monitoring.v3.UptimeCheckConfig.ContentMatcher

Optional. Used to perform content matching. This allows matching based on substrings and regular expressions, together with their negations. Only the first 4&nbsp;MB of an HTTP or HTTPS check's response (and the first 1&nbsp;MB of a TCP check's response) are examined for purposes of content matching.

Protobuf type google.monitoring.v3.UptimeCheckConfig.ContentMatcher

Information needed to perform a JSONPath content match. Used for ContentMatcherOption::MATCHES_JSON_PATH and ContentMatcherOption::NOT_MATCHES_JSON_PATH.

Protobuf type google.monitoring.v3.UptimeCheckConfig.ContentMatcher.JsonPathMatcher

Information needed to perform a JSONPath content match. Used for ContentMatcherOption::MATCHES_JSON_PATH and ContentMatcherOption::NOT_MATCHES_JSON_PATH.

Protobuf type google.monitoring.v3.UptimeCheckConfig.ContentMatcher.JsonPathMatcher

Information involved in an HTTP/HTTPS Uptime check request.

Protobuf type google.monitoring.v3.UptimeCheckConfig.HttpCheck

The authentication parameters to provide to the specified resource or URL that requires a username and password. Currently, only Basic HTTP authentication is supported in Uptime checks.

Protobuf type google.monitoring.v3.UptimeCheckConfig.HttpCheck.BasicAuthentication

The authentication parameters to provide to the specified resource or URL that requires a username and password. Currently, only Basic HTTP authentication is supported in Uptime checks.

Protobuf type google.monitoring.v3.UptimeCheckConfig.HttpCheck.BasicAuthentication

Information involved in an HTTP/HTTPS Uptime check request.

Protobuf type google.monitoring.v3.UptimeCheckConfig.HttpCheck

A status to accept. Either a status code class like "2xx", or an integer status code like "200".

Protobuf type google.monitoring.v3.UptimeCheckConfig.HttpCheck.ResponseStatusCode

A status to accept. Either a status code class like "2xx", or an integer status code like "200".

Protobuf type google.monitoring.v3.UptimeCheckConfig.HttpCheck.ResponseStatusCode

Information involved in sending ICMP pings alongside public HTTP/TCP checks. For HTTP, the pings are performed for each part of the redirect chain.

Protobuf type google.monitoring.v3.UptimeCheckConfig.PingConfig

Information involved in sending ICMP pings alongside public HTTP/TCP checks. For HTTP, the pings are performed for each part of the redirect chain.

Protobuf type google.monitoring.v3.UptimeCheckConfig.PingConfig

The resource submessage for group checks. It can be used instead of a monitored resource, when multiple resources are being monitored.

Protobuf type google.monitoring.v3.UptimeCheckConfig.ResourceGroup

The resource submessage for group checks. It can be used instead of a monitored resource, when multiple resources are being monitored.

Protobuf type google.monitoring.v3.UptimeCheckConfig.ResourceGroup

Information required for a TCP Uptime check request.

Protobuf type google.monitoring.v3.UptimeCheckConfig.TcpCheck

Information required for a TCP Uptime check request.

Protobuf type google.monitoring.v3.UptimeCheckConfig.TcpCheck

Builder for projects/{project}/uptimeCheckConfigs/{uptime_check_config}.

Builder for folders/{folder}/uptimeCheckConfigs/{uptime_check_config}.

Builder for organizations/{organization}/uptimeCheckConfigs/{uptime_check_config}.

Contains the region, location, and list of IP addresses where checkers in the location run from.

Protobuf type google.monitoring.v3.UptimeCheckIp

Contains the region, location, and list of IP addresses where checkers in the location run from.

Protobuf type google.monitoring.v3.UptimeCheckIp

The UptimeCheckService API is used to manage (list, create, delete, edit) Uptime check configurations in the Cloud Monitoring product. An Uptime check is a piece of configuration that determines which resources and services to monitor for availability. These configurations can also be configured interactively by navigating to the Cloud console, selecting the appropriate project, clicking on "Monitoring" on the left-hand side to navigate to Cloud Monitoring, and then clicking on "Uptime".

A stub to allow clients to do synchronous rpc calls to service UptimeCheckService.

The UptimeCheckService API is used to manage (list, create, delete, edit) Uptime check configurations in the Cloud Monitoring product. An Uptime check is a piece of configuration that determines which resources and services to monitor for availability. These configurations can also be configured interactively by navigating to the Cloud console, selecting the appropriate project, clicking on "Monitoring" on the left-hand side to navigate to Cloud Monitoring, and then clicking on "Uptime".

A stub to allow clients to do ListenableFuture-style rpc calls to service UptimeCheckService.

The UptimeCheckService API is used to manage (list, create, delete, edit) Uptime check configurations in the Cloud Monitoring product. An Uptime check is a piece of configuration that determines which resources and services to monitor for availability. These configurations can also be configured interactively by navigating to the Cloud console, selecting the appropriate project, clicking on "Monitoring" on the left-hand side to navigate to Cloud Monitoring, and then clicking on "Uptime".

Base class for the server implementation of the service UptimeCheckService.

The UptimeCheckService API is used to manage (list, create, delete, edit) Uptime check configurations in the Cloud Monitoring product. An Uptime check is a piece of configuration that determines which resources and services to monitor for availability. These configurations can also be configured interactively by navigating to the Cloud console, selecting the appropriate project, clicking on "Monitoring" on the left-hand side to navigate to Cloud Monitoring, and then clicking on "Uptime".

A stub to allow clients to do asynchronous rpc calls to service UptimeCheckService.

The UptimeCheckService API is used to manage (list, create, delete, edit) Uptime check configurations in the Cloud Monitoring product. An Uptime check is a piece of configuration that determines which resources and services to monitor for availability. These configurations can also be configured interactively by navigating to the Cloud console, selecting the appropriate project, clicking on "Monitoring" on the left-hand side to navigate to Cloud Monitoring, and then clicking on "Uptime".

The VerifyNotificationChannel request.

Protobuf type google.monitoring.v3.VerifyNotificationChannelRequest

The VerifyNotificationChannel request.

Protobuf type google.monitoring.v3.VerifyNotificationChannelRequest

A WindowsBasedSli defines good_service as the count of time windows for which the provided service was of good quality. Criteria for determining if service was good are embedded in the window_criterion.

Protobuf type google.monitoring.v3.WindowsBasedSli

A WindowsBasedSli defines good_service as the count of time windows for which the provided service was of good quality. Criteria for determining if service was good are embedded in the window_criterion.

Protobuf type google.monitoring.v3.WindowsBasedSli

A MetricRange is used when each window is good when the value x of a single TimeSeries satisfies range.min <= x <= range.max. The provided TimeSeries must have ValueType = INT64 or ValueType = DOUBLE and MetricKind = GAUGE.

Protobuf type google.monitoring.v3.WindowsBasedSli.MetricRange

A MetricRange is used when each window is good when the value x of a single TimeSeries satisfies range.min <= x <= range.max. The provided TimeSeries must have ValueType = INT64 or ValueType = DOUBLE and MetricKind = GAUGE.

Protobuf type google.monitoring.v3.WindowsBasedSli.MetricRange

A PerformanceThreshold is used when each window is good when that window has a sufficiently high performance.

Protobuf type google.monitoring.v3.WindowsBasedSli.PerformanceThreshold

A PerformanceThreshold is used when each window is good when that window has a sufficiently high performance.

Protobuf type google.monitoring.v3.WindowsBasedSli.PerformanceThreshold

The AlertPolicyService API is used to manage (list, create, delete, edit) alert policies in Cloud Monitoring. An alerting policy is a description of the conditions under which some aspect of your system is considered to be "unhealthy" and the ways to notify people or services about this state. In addition to using this API, alert policies can also be managed through Cloud Monitoring, which can be reached by clicking the "Monitoring" tab in Cloud console.

The Group API lets you inspect and manage your groups. A group is a named filter that is used to identify a collection of monitored resources. Groups are typically used to mirror the physical and/or logical topology of the environment. Because group membership is computed dynamically, monitored resources that are started in the future are automatically placed in matching groups. By using a group to name monitored resources in, for example, an alert policy, the target of that alert policy is updated automatically as monitored resources are added and removed from the infrastructure.

Manages metric descriptors, monitored resource descriptors, and time series data.

The Notification Channel API provides access to configuration that controls how messages related to incidents are sent.

The QueryService API is used to manage time series data in Stackdriver Monitoring. Time series data is a collection of data points that describes the time-varying values of a metric.

The Cloud Monitoring Service-Oriented Monitoring API has endpoints for managing and querying aspects of a workspace's services. These include the Service's monitored resources, its Service-Level Objectives, and a taxonomy of categorized Health Metrics.

The SnoozeService API is used to temporarily prevent an alert policy from generating alerts. A Snooze is a description of the criteria under which one or more alert policies should not fire alerts for the specified duration.

The UptimeCheckService API is used to manage (list, create, delete, edit) Uptime check configurations in the Cloud Monitoring product. An Uptime check is a piece of configuration that determines which resources and services to monitor for availability. These configurations can also be configured interactively by navigating to the Cloud console, selecting the appropriate project, clicking on "Monitoring" on the left-hand side to navigate to Cloud Monitoring, and then clicking on "Uptime".

The Aligner specifies the operation that will be applied to the data points in each alignment period in a time series. Except for ALIGN_NONE, which specifies that no operation be applied, each alignment operation replaces the set of data values in each alignment period with a single value: the result of applying the operation to the data values. An aligned time series has a single data value at the end of each alignment_period. An alignment operation can change the data type of the values, too. For example, if you apply a counting operation to boolean values, the data value_type in the original time series is BOOLEAN, but the value_type in the aligned result is INT64.

Protobuf enum google.monitoring.v3.Aggregation.Aligner

A Reducer operation describes how to aggregate data points from multiple time series into a single time series, where the value of each data point in the resulting series is a function of all the already aligned values in the input time series.

Protobuf enum google.monitoring.v3.Aggregation.Reducer

A condition control that determines how metric-threshold conditions are evaluated when data stops arriving. This control doesn't affect metric-absence policies.

Protobuf enum google.monitoring.v3.AlertPolicy.Condition.EvaluationMissingData

Operators for combining conditions.

Protobuf enum google.monitoring.v3.AlertPolicy.ConditionCombinerType

Specifies an ordering relationship on two arguments, called left and right.

Protobuf enum google.monitoring.v3.ComparisonType

The supported resource types that can be used as values of group_resource.resource_type. INSTANCE includes gce_instance and aws_ec2_instance resource types. The resource types gae_app and uptime_url are not valid here because group checks on App Engine modules and URLs are not allowed.

Protobuf enum google.monitoring.v3.GroupResourceType

Operational states for an internal checker.

Protobuf enum google.monitoring.v3.InternalChecker.State

Controls which fields are returned by ListTimeSeries.

Protobuf enum google.monitoring.v3.ListTimeSeriesRequest.TimeSeriesView

Indicates whether the channel has been verified or not. It is illegal to specify this field in a CreateNotificationChannel or an UpdateNotificationChannel operation.

Protobuf enum google.monitoring.v3.NotificationChannel.VerificationStatus

ServiceLevelObjective.View determines what form of ServiceLevelObjective is returned from GetServiceLevelObjective, ListServiceLevelObjectives, and ListServiceLevelObjectiveVersions RPCs.

Protobuf enum google.monitoring.v3.ServiceLevelObjective.View

The tier of service for a Workspace. Please see the service tiers documentation for more details.

Protobuf enum google.monitoring.v3.ServiceTier

What kind of checkers are available to be used by the check.

Protobuf enum google.monitoring.v3.UptimeCheckConfig.CheckerType

Options to perform content matching.

Protobuf enum google.monitoring.v3.UptimeCheckConfig.ContentMatcher.ContentMatcherOption

Options to perform JSONPath content matching.

Protobuf enum google.monitoring.v3.UptimeCheckConfig.ContentMatcher.JsonPathMatcher.JsonPathMatcherOption

Header options corresponding to the content type of a HTTP request body.

Protobuf enum google.monitoring.v3.UptimeCheckConfig.HttpCheck.ContentType

The HTTP request method options.

Protobuf enum google.monitoring.v3.UptimeCheckConfig.HttpCheck.RequestMethod

An HTTP status code class.

Protobuf enum google.monitoring.v3.UptimeCheckConfig.HttpCheck.ResponseStatusCode.StatusClass

The regions from which an Uptime check can be run.

Protobuf enum google.monitoring.v3.UptimeCheckRegion