v0.3.0

Natchez 0.3, as well as Updates to Allowed Headers and the inclusion of redacted headers not within the allow list.

What's Changed

• Upgrade Deps by @ChristopherDavenport in #22
• Update sbt-scala-native-crossproject, ... to 1.3.1 by @davenverse-steward in #25
• Update Natchez by @ChristopherDavenport in #23
• Add Deprecation To Accepted Headers by @ChristopherDavenport in #28
• Update deps by @ChristopherDavenport in #41
• Add additional allowedHeaders, make notIncluded headers by @ChristopherDavenport in #42
• Update sbt-scala-native to 0.4.14 by @davenverse-steward in #38

New Contributors

• @davenverse-steward made their first contribution in #25

Full Changelog: v0.2.2...v0.3.0

v0.3.0-RC1

Adds Deprecation header to allowed list, updates natchez version

What's Changed

• Upgrade Deps by @ChristopherDavenport in #22
• Update sbt-scala-native-crossproject, ... to 1.3.1 by @davenverse-steward in #25
• Update Natchez by @ChristopherDavenport in #23
• Add Deprecation To Accepted Headers by @ChristopherDavenport in #28
• Update deps by @ChristopherDavenport in #41

New Contributors

• @davenverse-steward made their first contribution in #25

Full Changelog: v0.2.2...v0.3.0-RC1

v0.2.2

Adding some more headers to include by default.

What's Changed

• Add More Headers by @ChristopherDavenport in #7

Full Changelog: v0.2.1...v0.2.2

v0.2.1

Builder Pattern is Good. No surprises there, now we are using it. Older methods are deprecated to push you to builders. Automatically add retry count to clients with the RetryMiddleware from Http4s. Best to apply retry before the client middleware for best clarity, otherwise it will not show up on errors which probably isn't what you want. Adds the ability to arbitrarily add tags to client spans, since those are created entirely by the middleware and not directly controlled by the user. Adds the ability to fully hide the url. In case your url has sensitive information that you would rather not end up in tracing. Client spans are not very informative without it, but you have other methods to enrich those yourself.

What's Changed

• Add Retry Count Support by @ChristopherDavenport in #4
• Add way to add extra tags to client request spans by @ChristopherDavenport in #5
• Include Ability to Opt Out of Url by @ChristopherDavenport in #6

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Some deficiencies in the 0.1.0 version quickly emerged. We were missing span.kind which is critical to distinguish spans.
The naming strategy directly contradicted the standard. So we went with a conservative default, but left it configurable to users.

Request and Response Tags being to be able to played with for client and servers. You have access the server span, so these should be largely unnecessary. But wanted to leave the power in your hands.

What's Changed

• Add Kind, and Custom Span Name Function by @ChristopherDavenport in #3

Full Changelog: v0.1.0...v0.2.0

v0.1.0

First Binary Compatible Release. Lets test this out and see how it goes.

What's Changed

• Use correct error tags by @ChristopherDavenport in #1

Full Changelog: v0.0.1...v0.1.0

v0.0.2

• Switch Exceptions to Otel Error Standards

v0.0.1

• Initial Extremely Experimental Release
• Server and Client Middlewares
• Need to make sure we are getting all the expected values. Help Very Appreciated checking that the http attributes we are using match up with The OpenTelemetry Spec