Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(normalization): Write default transaction source [INGEST-1511] #1354

Merged
merged 6 commits into from
Jul 28, 2022

Conversation

jjbayer
Copy link
Member

@jjbayer jjbayer commented Jul 28, 2022

For old SDK that do not yet send an event.transaction_info.source value, write the default "unknown" to the transaction payload.

For a specific group of SDKs that we expect to send many distinct transaction names (containing identifiers), omit the default, such that these transactions can be queried for explicitly in the product.

@jjbayer jjbayer marked this pull request as ready for review July 28, 2022 11:07
@jjbayer jjbayer requested review from a team, bitsandfoxes, k-fish and jan-auer and removed request for bitsandfoxes July 28, 2022 11:07
…1356)

Excludes more SDKs from transaction name extraction that are known to contain bad URLs.
* master:
  fix(metrics): Fix broken extraction of ops breakdown and conditional tagging (#1357)
  fix(unreal): Don't drop event in PoP relays [INC-181] [ISSUE-1558] (#1355)
@jan-auer jan-auer enabled auto-merge (squash) July 28, 2022 19:46
@jan-auer jan-auer merged commit 55356ec into master Jul 28, 2022
@jan-auer jan-auer deleted the feat/default-transaction-source branch July 28, 2022 20:01
tobias-wilfert pushed a commit that referenced this pull request Aug 9, 2022
In #1354, we introduced behavior that wrote back the default transaction
source (unknown) into the event during normalization.

Unfortunately, since the default qualifies as empty, this value was
still not serialized into the event payload.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants