-
Notifications
You must be signed in to change notification settings - Fork 3
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
qos-enclave health check logs should be a single line #388
Comments
This is an issue from an upstream library |
Created a PR, lets see if anyone responds aws/aws-nitro-enclaves-cli#544 |
If they decline the pr for some reason we can always parse and reserialise.
Would be unfortunate but at least there's an alternative way to fix this
…On Mon, 9 Oct 2023, 11:18 pm Zeke Mostov, ***@***.***> wrote:
It comes from this line
https://github.com/aws/aws-nitro-enclaves-cli/blob/a3c60d3fc7ccde599497082b3ab66d1c0f4476f0/src/enclave_proc_comm.rs#L332
—
Reply to this email directly, view it on GitHub
<#388 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRCCK7D7P3FABOZTL2ICE3X6QBULAVCNFSM6AAAAAA5YEOJJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJTGEYDGNZTGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently when
qos_enclave
logs the health check, it does so over many lines of prettified json.For ease of log ingestion/monitoring, could this be a single (unprettified) json line?
The text was updated successfully, but these errors were encountered: