The SDK should implement the following:
- a way to
H.recordException following the otel exception reporting spec.
- a way to instrument php/laravel logging libraries. if the php/laravel sdk supports logs natively, it would be great to route them to as LogRecords on
v1/logs, but if not, fine to support them as trace events.
as part of the exception implementation, if laravel libraries follow a common format for tracing HTTP request handlers, it would be great to wrap those as native otel traces.
We should build the SDK based on the opentelemetry sdk. There is a guide for php laravel specifically, so we should follow best practices here in terms of collecting the available data.
Requirements:
- a
init method that sets up the PHP instrumentation to collect console logs automatically.
- a
recordException method that allows capturing errors manually (see java sdk as an example).
- Laravel instrumentation that will hook into the framework to collect errors / logs automatically, without the need for a user to manually report errors.
Some getting started pointers on our docs! Please let us know if you have feedback, I'm happy to add to them.
The SDK should implement the following:
H.recordExceptionfollowing the otel exception reporting spec.v1/logs, but if not, fine to support them as trace events.as part of the exception implementation, if laravel libraries follow a common format for tracing HTTP request handlers, it would be great to wrap those as native otel traces.
We should build the SDK based on the opentelemetry sdk. There is a guide for php laravel specifically, so we should follow best practices here in terms of collecting the available data.
Requirements:
initmethod that sets up the PHP instrumentation to collect console logs automatically.recordExceptionmethod that allows capturing errors manually (see java sdk as an example).Some getting started pointers on our docs! Please let us know if you have feedback, I'm happy to add to them.