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

NH-34752 Update span layer, little refactor #134

Merged
merged 3 commits into from
Apr 20, 2023

Conversation

tammy-baylis-swi
Copy link
Contributor

Updates Python APM-produced span layers to be <KIND>:<NAME> and match what Java APM does. This is a prerequisite for implementing transaction filtering.

Example trace before this update uses these span layers:

  1. home_a/
  2. home_b/
  3. HTTP GET
  4. manual_instrumentation_django_a
  5. manual_instrumentation_django_b
  6. postgresql
  7. sqlite

Example trace after this update uses:

  1. SERVER:home_a/
  2. SERVER:home_b/
  3. CLIENT:HTTP GET
  4. INTERNAL:manual_instrumentation_django_a
  5. INTERNAL:manual_instrumentation_django_b
  6. postgresql
  7. sqlite

6 and 7 are expected as per improvements based on mrQ's requests (see also Slack thread).

This PR also does a little refactor of config file reading based on this PR comment.

Please let me know if any questions/suggestions!

@tammy-baylis-swi tammy-baylis-swi marked this pull request as ready for review April 18, 2023 23:01
@tammy-baylis-swi tammy-baylis-swi requested a review from a team April 18, 2023 23:01
Copy link
Member

@raphael-theriault-swi raphael-theriault-swi 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 case conversion revisit !

@tammy-baylis-swi tammy-baylis-swi merged commit 93fc0cf into main Apr 20, 2023
@tammy-baylis-swi tammy-baylis-swi deleted the NH-34752-update-span-layer branch April 20, 2023 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants