Test run parameters - Message size

[ohadkoren]

Description

Currently, the entire application is working without the message size parameter.

As a backend developer, we need to make sure the application is making her analyze process including the message size.

As a frontend developer, it needs to be presented on the following section:

• Home page:
  • New test run parameter, including custom input.
• "Experiment" page:
  • New column called "Message Size (KB)" inside the experiment table.
  • Add the message size to the "selected columns" popup section.
  • Add the message size to the charts tooltip and charts drop-down option presented.
• "All Experiments" page:
  • New column called "Message Size (KB)" inside the all-experiments table.

Predefined list of options in the UI
0 bytes, 1 byte, 2 bytes, 100 bytes, 1KB, 100KB, 200KB, 1MB, 2MB, 10MB
These values will be provided in bytes from the backend.
The user should be able to add more options as needed. (In bytes)
The dropdown should take the bytes that are given as input and show them in the correct unit.
The number itself in the dropdown should not exceed 3 digits. (500 KB is ok, 1024KB is not OK. Should be 1 MB).
Below is a JS library + usage snippet that can help with that.

const filesize = require('filesize');

function convertBytesToHumanReadable(bytesValue) {
    /**
     * Convert bytes to human-readable units with a maximum of 3 digits.
     */
    return filesize(bytesValue, {round: 3});
}

// Example usage:
const bytesValue1 = 500 * 1024; // 500 KB
const bytesValue2 = 1024 * 1024; // 1024 KB
console.log(convertBytesToHumanReadable(bytesValue1)); // Output: 500.000 KB
console.log(convertBytesToHumanReadable(bytesValue2)); // Output: 1.000 MB

Acceptance Criteria

We should consider the "message size" parameter throughout the entire application.

Tasks

• [API] Add message_size parameter #104
• [Curl] Add message size parameter #105
• [Nginx] Support post requests with body #106
• [Portal] Add message_size parameter #107
• message sizes list options api #117