Recording metrics

When you record a metric with the observability plugin, it must include a name and value. Optionally, it can also include attributes and a timestamp. To construct the attributes, use Attributes from the @opentelemetry/api.

Here are the options for recording metrics:

1
  LDObserve.shared.recordMetric(metric: .init(name: "elapsedTimeMs", value: 2200))

To learn more, read Observe.

When you record a metric with the observability plugin, it must include a name and value. Optionally, it can also include attributes and a timestamp. To construct the attributes, use Attributes from the @opentelemetry/api.

Here are the options for recording metrics:

1
  LDObserve.recordMetric(Metric("elapsedTimeMs", 2200))

To learn more, read LDObserve.

Here are the options for recording metrics:

1
const onClick = () => {
2
  const start = Date.now();
3
  doInterestingWork();
4
  const elapsed = Date.now() - start;
5
  LDObserve.recordGauge({name: "elapsedTimeMs", value: elapsed});
6
};

To learn more, read Observe.

When you record a metric with the observability plugin, it must include a name and value. Optionally, it can also include attributes and a timestamp. To construct the attributes, use Attributes from the @opentelemetry/api.

Here are the options for recording metrics:

1
  LDObserve.recordMetric({name: "elapsedTimeMs", value: 2200});

To learn more, read Observe.

Here are the options for recording metrics:

1
  Observe.RecordMetric(name, value, attributes);

To learn more, read Observe.

To record a metric, pass the Go context.Context, as well as the name, value, and optional attributes of the metric to the appropriate Record* function. For example, you might want to record the value for a point-in-time measurement, such as the current CPU utilization percentage, or for a counter, such as the number of cache hits. The optional attributes may include any attributes from the OpenTelemetry specification.

Metrics with the same name and attributes are aggregated using the OpenTelemetry SDK. To learn more, read the OTel documentation on the Metrics Data Model.

Here are the options for recording metrics:

1
  ldobserve.RecordMetric(ctx, "example-metric-name", 3.7)

To learn more, read RecordMetric, RecordCount, and RecordHistogram.

To record a metric, first create the metric within your application. The Metric interface includes a name, value, and optional tags. For example, you might create a metric for a point-in-time measurement, such as the current CPU utilization percentage, or for a counter, such as the number of cache hits.

Values with the same metric name and attributes are aggregated using the OpenTelemetry SDK. To learn more, read the OTel documentation on the Metrics Data Model.

1
const metric = {
2
  name: "exampleMetric",
3
  value: 42
4
}

Here are the options for recording metrics:

1
  LDObserve.recordMetric(metric);

To learn more, read Observe.

To record a metric, pass the name, value, and optional attributes to the appropriate record_* function. For example, you might want to record the value for a point-in-time measurement, such as the current CPU utilization percentage, or for a counter, such as the number of cache hits. The optional attributes may include any attributes from the OpenTelemetry specification.

Metrics with the same name and attributes are aggregated using the OpenTelemetry SDK. To learn more, read the OTel documentation on the Metrics Data Model.

Here are the options for recording metrics:

1
  observe.record_metric("example-metric-name", 3.7)

To learn more, read ldobserve.