Skip to content

Conversation

@kaylareopelle
Copy link
Contributor

Previously, it was difficult to tell what logging libraries had APM logs in context support. Now, it has its own table. We plan to add more logging libraries this quarter.

Previously, it was difficult to tell what logging libraries had APM
logs in context support. Now, it has its own table. We plan to add more
logging libraries this quarter.
@github-actions
Copy link

Hi @kaylareopelle 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local.

If you really require a preview url, reach out to one of the writers and they will generate one for you.

@kaylareopelle kaylareopelle changed the title chore: Add a section for log frameworks chore(ruby-agent): Add a section for log frameworks Oct 23, 2025
@kaylareopelle
Copy link
Contributor Author

moving back to a draft so I can preview locally tomorrow

@WriteMayur
Copy link
Contributor

netlify build fork

@svc-docs-eng-opensource-bot
Copy link
Contributor

✅ Your PR has been mirrored to our repository as PR #21984.
Commit: b5522169bef355504661d29a9c9c070b42981f38 (b552216)
Our workflows will run in the mirrored PR linked above.
🚀 If the build is successful, a Netlify preview will be available shortly at: https://kaylareopelle-ruby-logging-support--docs-website-netlify.netlify.app

@kaylareopelle
Copy link
Contributor Author

Thank you for triggering the netlify build! This looks good to me. Something that predates this PR, but would be nice to address someday would be to increase the width of the columns for the gem names to get them to fit on one line.

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