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

Update _index.md #27151

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jcayetano
Copy link
Contributor

Adding another Troubleshooting to check restrictions queries.

What does this PR do? What is the motivation?

Covering some extra steps to troubleshoot and checking data access for logs.

Merge instructions

Merge readiness:

  • Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

Adding another Troubleshooting to check restrictions queries.
@jcayetano jcayetano requested a review from a team as a code owner January 16, 2025 13:13
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@jhgilbert jhgilbert self-assigned this Jan 16, 2025
Copy link
Contributor

@jhgilbert jhgilbert left a comment

Choose a reason for hiding this comment

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

Approved with a few suggestions for grammar and style, thank you!

@@ -4,13 +4,19 @@ title: Logs Troubleshooting

If you experience unexpected behavior with Datadog Logs, there are a few common issues you can investigate and this guide may help resolve issues quickly. If you continue to have trouble, reach out to [Datadog support][1] for further assistance.

## Missing logs - data access restrictions

You cannot see any logs neither in the [Log Explorer][2] or [Live Tail][3]. This may be happening because your role is part of a restriction query.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
You cannot see any logs neither in the [Log Explorer][2] or [Live Tail][3]. This may be happening because your role is part of a restriction query.
You cannot see any logs in the [Log Explorer][2] or [Live Tail][3]. This may be happening because your role is part of a restriction query.


2. In **Pipelines**, hover over **Preprocessing for JSON logs**, and click the pencil icon.

3. Remove `timestamp` from the reserved attribute mapping list. The attribute is not being parsed as the official timestamp of the log during preprocessing.

{{< img src="logs/troubleshooting/preprocessing_json_timestamp.png" alt="The preprocessing for JSON logs configuration box with the date attributes, which includes timestamp by default" style="width:90%" >}}

2. Set up the [arithmetic processor][5] so that the formula multiples your timestamp by 1000 to convert it to milliseconds. The formula's result is a new attribute.
2. Set up the [arithmetic processor][7] so that the formula multiples your timestamp by 1000 to convert it to milliseconds. The formula's result is a new attribute.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
2. Set up the [arithmetic processor][7] so that the formula multiples your timestamp by 1000 to convert it to milliseconds. The formula's result is a new attribute.
2. Set up the [arithmetic processor][7] so that the formula multiplies your timestamp by 1000 to convert it to milliseconds. The formula's result is a new attribute.

I know this typo was already there, sorry we didn't catch it sooner!

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.

2 participants