The runtime handle the sink is resolved from.
Records a domain metric.
The runtime handle.
The metric name — the key it is grouped by.
Optionaldimensions: string[]
String dimensions to filter and group by.
Optionalmeasures: number[]
Numeric measurements to aggregate.
true when the data point was accepted.
Reports whether the capability is actually usable on this runtime.
The runtime handle.
true when calls will reach a real backing resource.
A capability backed by an optional resource answers false when that
resource was never provisioned. Implementations must document what each
method does in that state — degrade or throw — and must not vary it, since
a caller choosing between two implementations is relying on the answer
meaning the same thing in both.
Records one request.
The runtime handle.
The request measurement.
true when the data point was accepted.
A sink for measurements — durations, counts, statuses — meant to be aggregated rather than read back individually.
Remarks
Deliberately distinct from logging. A telemetry backend samples at volume, which is right for rates and percentiles and wrong for anything that must be read back verbatim; a log line is the opposite. Keeping them as two capabilities is what stops one being quietly used for the other's job.
Every write is best-effort and returns a boolean instead of throwing: telemetry must never be able to fail the request it is describing.
Author
Bayu Dwiyan Satria
Version
1.0.0
Since
1.0.0