hs-opentelemetry

hs-opentelemetry copied to clipboard

I've got an application instrumented with both hs-opentelemetry-instrumentation-wai and hs-opentelemetry-instrumentation-yesod. For the most part this works well, however I've found that the details of exceptions (exception message, exception backtrace, span...

spencerjanssen

Code detection is flaky when you define helpers for `inSpan`

3

If you define an `inSpan` helper function like: ```haskell myInSpan :: HasCallStack => Text -> IO a -> IO a myInSpan name action = inSpan name defaultSpanArguments action ``` Then...

parsonsmatt

The return value of `forceFlushTracerProvider` is `FlushResult`, but that type isn't exported so it can't be used, and this change fixes that.

Gabriella439

kakkun61

Extensibility for Propagators and Samplers

1

:wave: Hi there! We're just getting started with OpenTelemetry and are looking to emit OTel traces from our app and then us the AWS collector to export to X-Ray. This...

pbrisbin

Fix CI etc.

1

- resolve conflicts - update Makefile for stack.yaml - fix compiler error with GHC 8.10 - CI for GHC 8.10 - CI with Cabal - restore Nix environment - format...

kakkun61

Figure out how to get library versions without hardcoding them

7

iand675

While implementing metrics will presumably be more challenging, implementing logging looks much easier in the meantime. The basic `OpenTelemetry.Logging.Core.Log` type is there (although the `tracingDetails` field should be broken up...

spacekitteh

Metrics?

2

I'd love to start collecting metrics; is this in development at all?

spacekitteh

We [used to have a version of `inSpan''` that took an explicit `CallStack`](https://hackage.haskell.org/package/hs-opentelemetry-api-0.0.3.8/docs/OpenTelemetry-Trace-Core.html#v:inSpan-39--39-). However, in 0.1 [`inSpan''` no longer takes a `CallStack`](https://hackage.haskell.org/package/hs-opentelemetry-api-0.1.0.0/docs/OpenTelemetry-Trace-Core.html#v:inSpan-39--39-) (and seems to be identical to the type...

ocharles