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 have a question about the http.downloaded_bytes metric in Artillery.
I recently conducted a test using Artillery to compare the results with and without compression in Nest.js server.
However, when I ran the test to observe the compression results, the http.downloaded_bytes metric didn’t appear.
Interestingly, when I tested the same scenario using curl and Postman, I was able to see the downloaded bytes.
Could anyone explain why the http.downloaded_bytes metric isn’t showing up during the compression test with Artillery?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi everyone,
I have a question about the http.downloaded_bytes metric in Artillery.
I recently conducted a test using Artillery to compare the results with and without compression in Nest.js server.
However, when I ran the test to observe the compression results, the http.downloaded_bytes metric didn’t appear.
Interestingly, when I tested the same scenario using curl and Postman, I was able to see the downloaded bytes.
Could anyone explain why the http.downloaded_bytes metric isn’t showing up during the compression test with Artillery?
Here’s my environment:
Compression Test Log
Without compression
Compression middleware
scenario.yml
If you need any extra information, please tell me.
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions