Support Open Telemetry #203
Description
As a library, implementing Open Telemetry (OTel) can help users monitor their instances, see:
https://opentelemetry.io/docs/concepts/instrumentation/libraries/
To avoid the OTel overhead, probably that the best is to create a @whook/otel plugin that wraps some Knifecycle services:
- httpRouter: to monitor the router (with events to monitor routing, parsing, execution and transfert completion time)
- httpTransaction: to follow each transaction (child span of router ones)
- cron handlers
- consumer handlers
Logs may be reshape to be more adapted to OTel despite it sates that there is no standard/recommended format: https://opentelemetry.io/docs/specs/otel/logs/data-model/ .
Decide if the apm service is still relevant.
Beware to avoid implementing OTel probes that already exists for used libraries, see: https://opentelemetry.io/docs/concepts/instrumentation/zero-code/