TelemetryEvent
in package
AbstractYes
A telemetry event (CONTRACT.md §19).
PHP has no sealed keyword, so the closed-hierarchy guarantee §19.2 rule 3
relies on is carried structurally instead: every subclass is final, with a
fixed list of readonly promoted properties and no free-form array. There is
nowhere to put a token in a payload bound for a metrics backend.
Hooks are invoked on the calling path, so a sink must not block: §19.2 rule 4 makes buffering the caller's job so they can pick the policy. Every mature metrics library already buffers.
Tags
Table of Contents
Constants
- OUTCOME_FAILURE : mixed = 'failure'
- Outcome: the call failed, at any layer.
- OUTCOME_SUCCESS : mixed = 'success'
- Outcome: the call returned a usable response.
- REFRESH_FOLLOWER : mixed = 'follower'
- Refresh role: this caller waited on another's refresh.
- REFRESH_LEADER : mixed = 'leader'
- Refresh role: this caller performed the refresh.
Constants
OUTCOME_FAILURE
Outcome: the call failed, at any layer.
public
mixed
OUTCOME_FAILURE
= 'failure'
OUTCOME_SUCCESS
Outcome: the call returned a usable response.
public
mixed
OUTCOME_SUCCESS
= 'success'
REFRESH_FOLLOWER
Refresh role: this caller waited on another's refresh.
public
mixed
REFRESH_FOLLOWER
= 'follower'
REFRESH_LEADER
Refresh role: this caller performed the refresh.
public
mixed
REFRESH_LEADER
= 'leader'