| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Coverage Report for CI Build 27977604711Coverage decreased (-0.2%) to 89.606%Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Sorry, something went wrong.
There was a problem hiding this comment.
I am testing this and noticed that there are no INFO log messages for metrics/traces collection or upload, which in my opinion is nice to have to be able to confirm that things are working as expected and maybe help in deubgging in some scenarios.
Sorry, something went wrong.
There was a problem hiding this comment.
Thinking Out Loud: How can one configure 2 different endpoints, one for trace exportation and one for metrics?
Sorry, something went wrong.
What? In what way log messages are connected to metrics and traces? What am I missing here? |
Sorry, something went wrong.
- Add `OTelOpts` config struct - Add `internal/otel` package: Provider, Tracer, Meter, Shutdown, Noop - Add 5 metric instruments - Instrument `executeChain` and `executeTask` with spans and metrics - Wire real provider in `main.go` with graceful shutdown - `ValidateOTel()` validates endpoint scheme, ratio, and timeouts - Protocol auto-detected from URL scheme (grpc:// vs http(s)://) - Headers are YAML-only (prevents secrets in shell history) - Fallback to `Noop` provider on init failure
| Back | FazBrowse Home | New Git URL |
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.