On request from Remi L., I increased priority of this feature last week, and it is released today :-)

It is now possible to:

Export Http communications​

• Export a selection of Http communications, including:
  • Request and response headers and metadata
  • Requests and response bodies (embedded in base 64)
  • The name resolutions of the involved ips
  • The export is limited to 100 HTTP communications at once
  • Ex: https://jsonblob.com/5d065775-8daf-11e8-88f2-f13e4456ef7a

Beware though: if the request or response body was encoded (gzipped or chunked for instance), it is still encoded, as transmitted on the wire.

Import them back​

• Import back this export to another Whisperer, of UPLOAD type.
  • It is like magic, you get back your saved communications and can analyze them at peace.
  • You may import many exports at once by selecting many files or by drag&dropping them on the upload icon.
  • Beware though: if you import from different environments from the same time window to the same Whisperer.. you may have some IP clashes, and some strange results ;)

The first identified use cases​

• Being able to save a selection of requests performed by an integrated client to check non regression later on.
• Being able to compare different clients integration.
• Being able to export clients integration from production to its own environment to be able to create automated tests from them.

This feature, linked to the 'Diff' feature previously released adds even more power to Spider as a killer tool for integration :-)

Interested?​

Anybody can export. However, you need to have your own Whisperer of UPLOAD type to be able to import back.

• I created one for Remi for tests, ask one from me if you want.
• For now, I'd rather not give to everybody to right to create Whisperers.
• Once created, you'll have all configuration options to them, and will be able to share them with others (your team).
  • But only the owner of the Whisperer can upload to it.

Cheers, Thibaut

Network map got a small improvement:

• Now, clients with similar (or same) identification are merged on the map, as for servers replicas.
  • This reduces the amount of 'noise' on the map, and show a single client connecting with several IPs (many stations, many devices, or one moving device) as one single client.

This option is active when Merge option is active.

NB: This feature is not present on the sequence diagram.

I added information for easier reading of sequence diagrams:

The relative time since the beginning of the sequence diagram is now display right to the time axis.

Thanks Aless for the tip!

After the second/third processing of production statistics, we can say that, although they are very easy to generate, the processing of the screenshot export are slow and painful !

So I shifted priorities, and invested some time in Excel export :)

And now, all statistics information can be exported to an Excel spreadsheet in one click. They include:

• Stats metadata
• Main statistics with inclusion of Spider generated graphics as is
• Source data of the previous graphics (heatmap, distribution, evolution)
• And the most interesting: Pivot table with the grouped statistics
  • With the same color scale as on the website

Thanks https://github.com/guyonroche/exceljs for the very nice library!

Examples​

---

Response time statistics of GET parks/areas

Excel export:  Spider stats - Duration

---

Response time statistics on SIT1 by service, url, verb and status (truncated)

Excel export:  Spider stats - Duration, group by Server (merged), URL templates, Verb, Status

Enjoy! Thibaut

Special dedicace to Bertrand R.! :)

I added a new column 'links' in HTTP grid. For now, it tells you if Correlation Ids has been found on a communication, and, if yes, allow you to filter on them with one click, and even to open the related sequence diagram by clicking while holding shift.

Analysing Controls or Rights calls fan outs has never been simpler ;-)

Result:

Note: a new setting is needed to list Correlation Ids headers to watch. It is valued with Streetsmart correlation-token header by default in Streetsmart server configuration.

PS: Timeboxed in 3 hours ;)

I love React. Reuse of components is just so easy!

I added 'shortcuts' to filters in the columns headers of the grid. That will fasten your work and I hope improve the User Experience :-)

Nicolas C. suggested it, and I had it in my roadmap... but I never actually thought how to do it. And after some thinking, I found an solution so easy and reusing existing ones that... here are they, a couple of hours later =)

Enjoy!

Filter for items

Filter for range

First step autocompletion has been added to search inputs :) !! Now, you can type in the fields name much faster !

Next step... suggestion of values!

Quick win for easier reading! :) Thanks Ace!!

You may now perform a diff between selected items in Spider :)

• Differences are marked in yellow background.
• When content is compared, new data is in green, removed data in red, striked through.
• You can compare as many items as you want, they are all compared to the first one selected.
• There is no circuit breaker yet (tests in progress)... Diff may take a very long time or fail on too big payloads.
• Library used for Diff: https://github.com/kpdecker/jsdiff

Enjoy, and leave a comment! Especially for any bugs... this is first release, and will surely improve ;-)

First, select communications to compare, and click Compare icon:

Global tab show metadata from communications, yellow cells mark differences.

Headers tab shows diff in headers.

And Request bodies and Response bodies tabs show differences in formatted content.

Cheers, Thibaut

For next coming feature (comparison of items), I needed first to implement selection on grid.

Grid selection is now available:

• You can select records on grid
• Your selection is kept through time selection change, browser refresh, view change and so on.
• You can choose to see only your selection (specific filtering)
• And you can clear it.

More is coming, stay tuned