JSON reports: making it easy to process results in detail
You can now generate your ByteBlower reports in JSON format ! This is a beta feature, meaning that we are still actively developing it. We are already releasing this feature because we are convinced that it will bring you great benefits, even in its current state. Also, we 'd love to hear from you what you think of the JSON reports.
Enable the JSON results in the Preferences:
Remember, you can re-generate reports, using existing test data ! Click here to learn how to regenerate GUI reports
Interactive reports: getting a good grip on things
ByteBlower reports contain a lot of information. It may be difficult to interpret the graphs, especially in the case of large tests. Some plots appear to be stacked right over each other, hiding crucial info.
While we can't make your screen any larger, we can help you identify the events that matter.
This new release transforms all 6 results over time into interactive graphs. You can zoom in on them, hide plots you are not interested in and easily read the exact value at each point. An example of the new reports:
New tests use this interactive format by default, but we haven't forgotten your old results. Do you have an archived report you couldn't quite make sense of? You can regenerate it now in the report and inspect it in more depth.
Click here to see our Knowledge Base article about how to regenerate GUI reports.
When running tests, you often want a capture to investigate what is happening on your DUT/setup. You can now capture on the traffic ports through the GUI. Simply click to start the capture and all data is saved directly onto your hard drive; it's just a matter of opening Wireshark to start debugging. Below is an animated gif that shows how it's done:
Server Update Wizard
Updating your ByteBlower Server is now easier than ever! Even servers that have no direct connection with the internet can now be updated via the GUI. The new Server Update Wizard is available in the Server View. Here’s how it works:
Reports from a stopped CLT
Stopping the ByteBlower CLT used to be a tricky process. The only way to do it was through control-c, but this leaves you without a report. It is also annoying, especially when working with headless systems.
As of this release, you can now restart the ByteBlower-CLT with the regenerate option. The CLT will then regenerate the last report. It generates all available report types by default, but it also accepts a list of format types.
What's coming next?
The next version is already in the works and will be released in the next few months. Some of the new features you can expect:
- Wi-Fi details (RSSI/BSSID/...) in API where available
- JSON reports preview
You can download this version of the GUI here: https://setup.byteblower.com/software.html#GUI
Information on how to use the CLT version of the GUI: Introduction to ByteBlower CLT
- [Reporting] JSON reports.
- Initializing test-runs with many frames goes faster. The 'improving filter' requests less info from the ByteBlower server
- The TCP goodput (or Layer 5) rate was handled differently than all other results over tine. This caused artifacts in the Report. Everything is the same now, thus fixing the artifacts.
- Frames below the minimum 60 bytes are padded before transmitting.
- [Reporting] JSON reports. (beta feature)
- [Meeting Point]: When a single Wireless Endpoint returns corrupt information, the MeetingPoint keeps refreshing now.
- [UI]: The GUI is more lenient now regarding allowed IPv6 address format.
- [Reporting]: The CSV report didn't always include the OOS results over time. They do now.
- [Reporting]: Cleanup of the CSV format. Not all sections used the same title format (TCP Info, TCP results over time, HTTP Results overtime), added a newline as a separator between HTTP and TCP results over time.
- [UI] Due to miscalculation, the IPv6 traffic class was limited to 0x80
- [CLT] The CLT now uses up to 1Gbyte of heap-space, just the same the ByteBlower GUI. This avoids the CLT going out of memory where the GUI succeeds.
- [UI] Only show valid battery levels.
- [UI] You can now also use the support tool or update a ByteBlower server that isn't running.
- [Reporting] The time-axis correctly counts the days in multiday tests
- Fixed nullpointer exception that happened when a test was cancelled promptly after being started.
- [Reporting] Fixed the Aggregate Tcp charts on MacOs. The embedded browser had difficulties with the minified script.
- [Reporting] The first sample of the Latency distribution wasn't shown.
- [Reporting] In the CSV output we've restored the headers and documentation of the "Out Of Sequence overview results table" and "Latency overview results table".
- [UI] The GUI report lists the configured duration of a FrameBlasting flow.
- [UI] The units are displayed on the time-axis in the graphical report
- [UI] The title of the FrameBlasting charts now shows source and destination
- [UI] The Hex text fields in the FrameView are easier to use. You don't need to fill in the leading zeros anymore.
- [UI] The edit button in the FrameBlasting View is disabled when the template has no frames.
- [Reporting] Reduced memory consumption when generating the HTML report.
- [Reporting] The FrameBlasting tables show all frame sizes even when multiple sizes are configured.
- [Reporting]: Fixed NullPointer exception while generating report of an RFC2544 test.
- [Reporting]: Fixed Frame Blasting Throughput results over time in CSV reports.
- [Reporting]: Interactive graphs.
- [Server View]: You can now capture network traffic from the popup menu in the Server View.
- [Server View]: Updating a server is now easier than ever. We added a new wizard explaining what will be done. We made it more robust and usable in various lab networks.
- [General]: The currently open project is saved regularly now. You can open the most recent project from the file menu.
- [CLT]: Added an option to regenerate the report on the latest CLT run.
- [Archive View]: When new reports are generated, they will now immediately become visible in the table.
- [About box]: Third-party libraries used have been documented. You can find them in our legal info for ByteBlower plug-ins.
- [General]: Reduced number of API calls to the ByteBlower Server for TCP tests. This will particularly benefit larger tests.
- [General]: NAT entries are kept live until right before the start of the test.
- [General]: The scenario isn’t stopped when the same server or meeting point is accessed from multiple FQDNs.
- [Archive View]: You can now regenerate multiple reports by selecting multiple tests.
- [Reporting]: For Linux users, interactive charts are only visible using an external browser.