autometrics-go icon indicating copy to clipboard operation
autometrics-go copied to clipboard

Easily add metrics to your system -- and actually understand them using automatically customized Prometheus queries

Results 9 autometrics-go issues
Sort by recently updated
recently updated
newest added

If not already possible, i would like for the metrics to be namespaced if a namespace option was specified ``` autometrics.Init( autometrics.WithNamespace("imaginary_application"), ) ``` `function_calls_duration_seconds_count` would become `imaginary_application_function_calls_duration_seconds_count` if this...

Pending #47 merge. Once the PR is merged, the ability to inject a new trace ID/span ID into an Echo context will only happen through a middleware library, to properly...

Not entirely sure what the support is like upstream: https://github.com/open-telemetry/opentelemetry-go/issues/559

enhancement

Mostly reading information there and making sure to capture it if present https://www.w3.org/TR/trace-context/

This is useful for the middleware usages, where the instrumentation is actually written by the user, but would still want the doc comments to contain links to prometheus and stuff.

See https://github.com/autometrics-dev/autometrics-shared/pull/61

Pending #47 merge. Once the PR is merged, the ability to inject a new trace ID/span ID into a Gin context will only happen through a middleware library, to properly...

https://github.com/autometrics-dev/autometrics-shared

documentation

It is important to help potential users assess the performance impact of the library. I suppose we could add an extra script to the example app that also measures the...