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

fix(logs in context): attempt to clarify what LIC is #5860

Merged
merged 7 commits into from
Jan 28, 2022

Conversation

zuluecho9
Copy link
Contributor

This was related to some user type capabilities work, where we were tryin to get more clear on what user types had available, and it seemed that the 'logs in context' doc could use a little more clarity on what exactly it did for customers (e.g., that logs data appears in other areas in the UI, like APM and infra UI). The reason this was important is because there's been a lot of discussion about which user types have which functionality and we link to this doc from the user type doc. I don't have a lot of confidence in what I did (not that knowledgeable about logs or logs in context) but hope was that it would spark some more eyes on some aspects I found confusing.
Other changes:
• Some places in doc, like procedure, seemed focused mainly on APM only so I tried to make it more clear it was about APM and infra agents.
• The procedure was a little confusing to me; I made an attempt to improve it but I am still not sure how the 'enable distributed tracing' and 'see the APM agent docs' stuff is related, because the 'enable DT' doesn't seem to be mentioned in the APM-specific docs. That could probably be clearer.
• Some minor readability edits as I saw them.

@zuluecho9 zuluecho9 added content requests related to docs site content from_tw Identifies issues/PRs from Tech Docs writers labels Jan 28, 2022
@zuluecho9 zuluecho9 self-assigned this Jan 28, 2022
@github-actions
Copy link

Hi @zuluecho9 👋
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.

Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes).

@github-actions github-actions bot added this to Hero to triage in Docs PRs and Issues Jan 28, 2022
@zuluecho9 zuluecho9 moved this from Hero to triage to In progress/being reviewed (by Hero or any TW) in Docs PRs and Issues Jan 28, 2022
barbnewrelic
barbnewrelic previously approved these changes Jan 28, 2022
Copy link
Contributor

@barbnewrelic barbnewrelic left a comment

Choose a reason for hiding this comment

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

Just a few comments, take 'em or leave 'em. Really appreciate a fresh pair of eyes on this doc!

@gatsby-cloud
Copy link

gatsby-cloud bot commented Jan 28, 2022

Gatsby Cloud Build Report

docs-website-develop

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 21m

@zuluecho9 zuluecho9 merged commit 455c0c0 into develop Jan 28, 2022
@zuluecho9 zuluecho9 deleted the Logs-in-context-description branch January 28, 2022 22:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content requests related to docs site content from_tw Identifies issues/PRs from Tech Docs writers
Projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants