You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found in our vault audit log there are some "corrupted" log entry, which is very long with recursive structure, here is an example: super long log entry.
It seems to be another multithread issue to me. There are totally 15 entries in our one-month audit log. It brings a lot of trouble to our log parsing infrastructure, as if you try to parse the json, thousands of keys could be parse from one single line.
This issue happened also before I adopted the customized build for vault hanging issue.
Regards,
The text was updated successfully, but these errors were encountered:
Hi,
I found in our vault audit log there are some "corrupted" log entry, which is very long with recursive structure, here is an example: super long log entry.
It seems to be another multithread issue to me. There are totally 15 entries in our one-month audit log. It brings a lot of trouble to our log parsing infrastructure, as if you try to parse the json, thousands of keys could be parse from one single line.
This issue happened also before I adopted the customized build for vault hanging issue.
Regards,
The text was updated successfully, but these errors were encountered: