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

[Heartbeat] Non-UTF8 HTTP Response Bodies Silently Disappear #15647

Closed
andrewvc opened this issue Jan 17, 2020 · 2 comments
Closed

[Heartbeat] Non-UTF8 HTTP Response Bodies Silently Disappear #15647

andrewvc opened this issue Jan 17, 2020 · 2 comments
Labels
bug Heartbeat Stalled Team:obs-ds-hosted-services Label for the Observability Hosted Services team

Comments

@andrewvc
Copy link
Contributor

We can't do much with non-UTF8 response bodies in terms of outputting them to the console or ES since the go JSON encoder will replace them with empty strings (and ES won't index them anyway).

However we should document this behavior and possible add a new field http.response.body.encoding field that shows the encoding of the body.

@andrewvc andrewvc added bug Heartbeat Team:obs-ds-hosted-services Label for the Observability Hosted Services team labels Jan 17, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/uptime (:uptime)

@botelastic
Copy link

botelastic bot commented Dec 21, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Heartbeat Stalled Team:obs-ds-hosted-services Label for the Observability Hosted Services team
Projects
None yet
Development

No branches or pull requests

3 participants