v1.5.6

• 🐞BUG FIX: v1.5.4 introduced a bug where exits were being caught and the span annotated, but then control flow continued as if the exit had not occurred. We now exit with the same reason that was caught, so control flow is unchanged.

Full Changelog: v1.5.5...v1.5.6

v1.5.5

What's Changed

• Catch throws, stringify thrown values and exit reasons for reporting by @erszcz in #149

Full Changelog: v1.5.4...v1.5.5

v1.5.4

Catch unhandled Erlang exits and add an error status to the span.

What's Changed

• Set error on a span with an unhandled :erlang.exit() by @erszcz in #148

New Contributors

• @erszcz made their first contribution in #148

Full Changelog: v1.5.3...v1.5.4

v1.5.3

• Bumps o11y version to v0.2.4 which includes an add_event method that processes the attributes given to it the same way with_span does.

Full Changelog: v1.5.2...v1.5.3

v1.5.2

v1.5.2

• Fixes a bug which included input parameters you didn't ask for in the span attributes.

Full Changelog: v1.5.1...v1.5.2

v1.5.1

• Fixes a bug with missing attrs_version

Full Changelog: v1.5.0...v1.5.1

v1.5.0

• 🚨 The decorator now uses the O11y.set_attribute(s) functions to set attributes on spans. This means that the attribute processing logic that was here previously has been migrated there. However, there are some backwards incompatible changes listed below.
• 🚨 The decorator no longer supports nested attributes in the include option. The O11y set_attribute and set_attributes functions should now be used to handle more complex attribute specifications. The SpanAttributes protocol in particular is what I recommend if you need to extract a subset of fields from an object. The example below will add only user.id and user.name to the span attributes.

defmodule User do
  @derive {O11y.SpanAttributes, only: [:id, :name]}
  defstruct [:id, :name, :email, :password]
end

defmodule UserFactory do
  use OpenTelemetryDecorator

  @decorate with_span("UserFactory.create", include: [:user])
  def create() do
    user = %User{id: 1, name: "Bob", email: "[email protected]", password: "secret"}
    {:ok, user}
  end
end

• 🚨 Changes the default attrs_version to "v2". You can override this with config :open_telemetry_decorator, attrs_version: "v1", but that only affects usages of Attribtues directly.
• ⚠️ Changes AttributesV2 to use the O11y.set_attribute(s) functions. The attribute processing logic that was here previously has been migrated there. However, there are some backwards incompatible changes listed below.
• ⚠️ Changed functionality: the error attribute is no longer treated differently from other attributes. It will be namespaced or prefixed as expected. If you're using Honeycomb this field will be automatically derived from the span's status_code, so you don't need to (and probably shouldn't) set it manually. Instead, use O11y.set_error/1 to set the status code to "error" and message to the provided (string or exception) value.
• ⚠️ Changed functionality: maps and structs given to Attributes.set/2 will be flattened and prefixed with the given name. e.g.

params = %{key: "value"}
Attributes.set(:params, params)
# Becomes
%{"params.key" => "value"}

Full Changelog: v1.4.13...v1.5.0

v1.4.13

• Updates O11y dependency to v0.1.4 to fix an issue with setting error messages on spans.

Full Changelog: v1.4.12...v1.4.13

v1.4.12

v1.4.12

• Updates decorator to use the o11y version of start and end span
• Refactor tests to use O11y.TestHelper and the available structs for asserting on span conents.

Full Changelog: v1.4.11...v1.4.12

v1.4.11

v1.4.11

Clean up after ourselves instead of right before setting the status

I didn't realize Span.end_span does not change the current span, which is why when the parent catches the reraise it had the wrong span as the current span.
We're starting the span in a place where we can hold on to it so we can manually update the current span to the parent so that callers that aren't using the decorator have the correct current span.

Full Changelog: v1.4.10...v1.4.11