Skip to main content
Drupal API
User account menu
  • Log in

Breadcrumb

  1. Drupal Core 11.1.x
  2. MetricConfigResponse.php

function MetricConfigResponse::setSchedules

A single metric may match multiple schedules. In such cases, the schedule that specifies the smallest period is applied. Note, for optimization purposes, it is recommended to use as few schedules as possible to capture all required metric updates. Where you can be conservative, do take full advantage of the inclusion/exclusion patterns to capture as much of your targeted metrics.

Generated from protobuf field <code>repeated .opentelemetry.proto.metrics.experimental.MetricConfigResponse.Schedule schedules = 2;</code>

Parameters

\Opentelemetry\Proto\Metrics\Experimental\MetricConfigResponse\Schedule[]|\Google\Protobuf\Internal\RepeatedField $var:

Return value

$this

File

vendor/open-telemetry/gen-otlp-protobuf/Opentelemetry/Proto/Metrics/Experimental/MetricConfigResponse.php, line 164

Class

MetricConfigResponse
Generated from protobuf message <code>opentelemetry.proto.metrics.experimental.MetricConfigResponse</code>

Namespace

Opentelemetry\Proto\Metrics\Experimental

Code

public function setSchedules($var) {
    $arr = GPBUtil::checkRepeatedField($var, \Google\Protobuf\Internal\GPBType::MESSAGE, \Opentelemetry\Proto\Metrics\Experimental\MetricConfigResponse\Schedule::class);
    $this->schedules = $arr;
    return $this;
}

API Navigation

  • Drupal Core 11.1.x
  • Topics
  • Classes
  • Functions
  • Constants
  • Globals
  • Files
  • Namespaces
  • Deprecated
  • Services
RSS feed
Powered by Drupal