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
After using the json input format for some load testing, I realized it would be considered valid json Lines input, since it consists of newline-separated JSON objects;
For clarity, and to improve the visibility of json Lines as well as its standardization, should the json input format be mentioned as json Lines in the Vegeta documentation? Without the context of the jsonl file format, passing multiple json objects like this rather than something like a list seems a little arbitrary.
The text was updated successfully, but these errors were encountered:
Hi,
After using the json input format for some load testing, I realized it would be considered valid json Lines input, since it consists of newline-separated JSON objects;
For clarity, and to improve the visibility of json Lines as well as its standardization, should the json input format be mentioned as json Lines in the Vegeta documentation? Without the context of the jsonl file format, passing multiple json objects like this rather than something like a list seems a little arbitrary.
The text was updated successfully, but these errors were encountered: