Calling this method will report an error in Highlight and map it to the current session being recorded.
A common use case for H.error is calling it right outside of an error boundary.
https://docs.highlight.run/grouping-errors for more information.
Record arbitrary metric values via as a Gauge. A Gauge records any point-in-time measurement, such as the current CPU utilization %. Values with the same metric name and attributes are aggregated via the OTel SDK. See https://opentelemetry.io/docs/specs/otel/metrics/data-model/ for more details.
Record arbitrary metric values via as a Histogram. A Histogram efficiently records near-by point-in-time measurement into a bucketed aggregate. Values with the same metric name and attributes are aggregated via the OTel SDK. See https://opentelemetry.io/docs/specs/otel/metrics/data-model/ for more details.
Record arbitrary metric values via as a Counter. A Counter efficiently records an increment in a metric, such as number of cache hits. Values with the same metric name and attributes are aggregated via the OTel SDK. See https://opentelemetry.io/docs/specs/otel/metrics/data-model/ for more details.
Record arbitrary logs from your own integrations or manual. Useful when you don't want to emit a console log to the browser dev tools but still want to report a custom log.
Record arbitrary metric values via as a UpDownCounter. A UpDownCounter efficiently records an increment or decrement in a metric, such as number of paying customers. Values with the same metric name and attributes are aggregated via the OTel SDK. See https://opentelemetry.io/docs/specs/otel/metrics/data-model/ for more details.
Start the observability data capture when running in manualStart mode.
Can safely be called before the SDK has initialized (e.g. before the
plugin registers): the call resolves once the SDK is attached and
started, without throwing.
Starts a new span for tracing in Highlight. The span will be ended when the
end() is called on the span. It returns whatever is returned from the
callback function.
H.startManualSpan('span-name', options, (span) => {
span.addEvent('event-name', { key: 'value' })
span.setAttribute('key', 'value')
await someAsyncFunction()
span.end()
})
Starts a new span for tracing in Highlight. The span will be ended when the callback function returns.
Stop the observability data capture.
Can safely be called before the SDK has initialized; before start()
it cancels a pending start instead of throwing.
OptionalgetAdds attributes to all telemetry recorded from now on: every span (including automatically instrumented ones such as document load, fetch/XHR, clicks and page views), log, error and metric.
Calling it again merges with the attributes already set; a null or
undefined value removes that key. Attributes passed to an individual
call (for example recordLog metadata or metric attributes) take
precedence over these. Keys in namespaces the SDK sets itself
(highlight.*, launchdarkly.*, session.*, context.contextKeys.*)
are ignored.
Attributes are held in memory for the current page load only: they are never persisted, and a full page load starts without them.
Each attribute is also added to every metric, so a value with many distinct values (such as a user ID) creates as many metric series.
Record arbitrary metric values via as a Counter. A Counter efficiently records an increment in a metric, such as number of cache hits. Values with the same metric name and attributes are aggregated via the OTel SDK. See https://opentelemetry.io/docs/specs/otel/metrics/data-model/ for more details.