Ivan Santos

Working example here: https://github.com/pragmaticivan/nestjs-otel-prom-grafana-tempo

Nice! Will keep that in mind for sure. Same for supporting Fastify.

I have a working version of that change: ```go type Config struct { SpanExporterEndpoint string `env:"OTEL_EXPORTER_OTLP_SPAN_ENDPOINT,default=0.0.0.0:4317"` SpanExporterEndpointInsecure bool `env:"OTEL_EXPORTER_OTLP_SPAN_INSECURE,default=false"` ServiceName string `env:"SERVICE_NAME"` ServiceVersion string `env:"SERVICE_VERSION,default=unknown"` Headers map[string]string `env:"OTEL_EXPORTER_OTLP_HEADERS"` MetricExporterEndpoint string...

Any plans to implement optional save on redirects? Maybe that can be a new property in the initializer function?

So imagine that it's a commit: ``` My title is here * Description of my commit 1 * Description of my commit 2 ``` If you follow Git commit standard...

Here's an example of a Commit that can become a PR: ``` [123] fixing node gh weird issue Fixes #123 ## Why is this change necessary? Because it's not working...

`[123] fixing node gh weird issue` becomes the title of the PR, and the rest becomes the description of the PR.

Are PRs welcome for that? I only need the metrics collection for Prometheus and will allow the UI in a different port.

When I started using metal.js, I got confused because of that. I agree with @fernandosouza Also, IMHO as a beginner with that would be easier to compare with JSX implementation...

cc @Robert-Frampton