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.

Sign up for GitHub

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

Jump to bottom

Additional troubleshooting suggestion for the Azure Monitor Ingestion client library #32562

Closed
robertparker9 opened this issue Oct 18, 2023 · 2 comments · Fixed by #32591
Closed

Additional troubleshooting suggestion for the Azure Monitor Ingestion client library #32562

robertparker9 opened this issue Oct 18, 2023 · 2 comments · Fixed by #32591
Assignees
@pvaneck
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor Monitor, Monitor Ingestion, Monitor Query question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@robertparker9
Copy link

robertparker9 commented Oct 18, 2023 •
edited

Is your feature request related to a problem? Please describe.
The log ingestion API can return 204 but no log entry is created. One possible cause for this is that the json body parameter is not an array.

Describe the solution you'd like
The "Troubleshooting missing logs" section needs updating to say only a json array works (it currently says "data should be in the form of a JSON object or array")

Describe alternatives you've considered
n/a

Additional context
n/a
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 18, 2023
@catalinaperalta catalinaperalta added bug This issue requires a change to an existing behavior in the product in order to be resolved. Monitor Monitor, Monitor Ingestion, Monitor Query and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Oct 18, 2023
@github-actions github-actions bot removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Oct 18, 2023
@catalinaperalta catalinaperalta added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that needs-triage This is a new issue that needs to be triaged to the appropriate team. and removed bug This issue requires a change to an existing behavior in the product in order to be resolved. labels Oct 18, 2023
@github-actions github-actions bot removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Oct 18, 2023
@catalinaperalta
Copy link
Member

Thanks for reaching out @robertparker9 ! Looping in @pvaneck to take a look

@pvaneck pvaneck mentioned this issue Oct 20, 2023
Merged
@pvaneck
Copy link
Member

pvaneck commented Oct 20, 2023

Thanks for the feedback @robertparker9. You are right as that text is misleading. I went ahead and created a PR to update the text, and add a check to the upload method to verify the type for logs: #32591

@github-actions github-actions bot locked and limited conversation to collaborators Jan 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pvaneck pvaneck

Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Monitor Monitor, Monitor Ingestion, Monitor Query question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Monitor][Ingestion] Add check for logs input type pvaneck/azure-sdk-for-python
3 participants
@pvaneck @catalinaperalta @robertparker9