Support for transactions #842
Conversation
solnic
force-pushed
the
solnic/support-for-transactions
branch
from
db95d53 to
78c75f0
Compare
solnic
force-pushed
the
solnic/support-for-transactions
branch
from
795d4b4 to
11d2662
Compare
| @@ -1,7 +1,7 @@ | |||
| defmodule Sentry.Options do | |||
| @moduledoc false | |||
|
|
|||
| @send_event_opts_schema_as_keyword [ | |||
| @common_opts_schema_as_keyword [ | |||
There was a problem hiding this comment.
Can you link to the docs that say that sample rate and before_send callbacks don't applly to transactions?
There was a problem hiding this comment.
@solnic this is still pending.
solnic
force-pushed
the
solnic/support-for-transactions
branch
from
11d2662 to
abb15eb
Compare
- Add Transaction struct - Add Sentry.send_transaction - Add support for collecting transactions in tests
solnic
force-pushed
the
solnic/support-for-transactions
branch
from
649a6be to
ef59c6f
Compare
| data: map(), | ||
|
|
||
| # Interfaces | ||
| spans: [Span.t()], |
There was a problem hiding this comment.
A transaction without spans is ok?
There was a problem hiding this comment.
@whatyouhide yes! the only really required piece of span information is meant to go to context.trace which is why I defined it as a required map in the type spec. spans list is only needed when you have child spans, and that's not always the case.
| |> Map.merge(%{ | ||
| platform: "elixir", | ||
| sdk: %{ | ||
| name: "sentry.elixir", | ||
| version: Application.spec(:sentry, :vsn) | ||
| } | ||
| }) |
There was a problem hiding this comment.
Can you elaborate on why this is necessary?
There was a problem hiding this comment.
@whatyouhide I just followed what we do for events, and since a transaction is an event + span info, then I thought it's a good idea to add platform and sdk information too. I'm not sure if it's strictly required though - I'll double check it.
This was extracted from #784