Add support for file tracers?

[lublak]

Currently we only can send traces to a server:

It would be nice to have a file based tracer:

https://go.dev/blog/execution-traces-2024

Note: There is a nice tool to view these traces:

https://github.com/dominikh/gotraceui

file.path
file.rotate
file.rotate_max_age_days

[jem-davies]

Having an in-built tracer 'file' would be a good addition I think, like we have for the file cache . We state on the documentation page for the file cache that it is intended to be used for development and debugging purposes only.

I think that you might be mixing up two different types of 'tracing' here though. The links you provide talk about execution traces which would be typically used for profiling a golang program's low-level runtime events.

But the bento tracing components are used to configure solutions such as open telemetry collector - which are used to capture distributed tracing events across services.

[lublak]

@jem-davies "execution traces which would be typically used for profiling a golang program's low-level runtime events"

Yes, I know that generally speaking it is not the same as Bento tracing. But I generally came across it through ‘file’ tracing. The question is, of course, whether there is something along these lines that is an open standard and also has visualisation applications.

An alternative idea would be a ‘bento’ tracer. So instead of a file:

Health Checks

Bento serves two HTTP endpoints for health checks:

/ping can be used as a liveness probe as it always returns a 200.
/ready can be used as a readiness probe as it serves a 200 only when both the input and output are connected, otherwise a 503 is returned.

Tracing

Bento exposes tracing on /traces (which also could be used with a "file-upload"?