Skip to content

Add: Request ID to rack related events#1111

Closed
tvec wants to merge 2 commits intogetsentry:masterfrom
tvec:tv/add-request-ids-to-tags
Closed

Add: Request ID to rack related events#1111
tvec wants to merge 2 commits intogetsentry:masterfrom
tvec:tv/add-request-ids-to-tags

Conversation

@tvec
Copy link
Copy Markdown
Contributor

@tvec tvec commented Nov 24, 2020

Description

  • Moved the initial logic from Add request id to headers if exists #1033 for request_id to shared utils
  • New Feature: Add request_id tags (when present) to Rack event
    • Added to both Sentry::Event & Raven::Event namespaces

Why

Testing

request_id_tags_example

@codecov-io
Copy link
Copy Markdown

codecov-io commented Nov 24, 2020

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.05%. Comparing base (44f347e) to head (c46ef35).
⚠️ Report is 1331 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1111      +/-   ##
==========================================
+ Coverage   98.04%   98.05%   +0.01%     
==========================================
  Files         144      147       +3     
  Lines        6101     6133      +32     
==========================================
+ Hits         5982     6014      +32     
  Misses        119      119              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

tvec added 2 commits November 24, 2020 09:46
- moved request id logic to the shared utils
- add request_id tagging when encountering a Rack related Event
- moved request id logic to the shared utils
- add request_id tagging when encountering a Rack related Event
@tvec tvec force-pushed the tv/add-request-ids-to-tags branch from 487f9de to c46ef35 Compare November 24, 2020 14:46
Copy link
Copy Markdown
Contributor

@st0012 st0012 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for the work 👍

@st0012 st0012 modified the milestone: 4.0.0 Nov 26, 2020
Copy link
Copy Markdown
Contributor

@st0012 st0012 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah sorry, in order to make tracking/reverting the change easier (not likely though, just in case), can you split the changes into 2 PRs? one for each gem.

@tvec
Copy link
Copy Markdown
Contributor Author

tvec commented Nov 30, 2020

Yep, can do!

EDIT: see #1119 & #1120

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.

3 participants