When finding issues on Flowbird production deployment of Spider, we noticed that there were a small pourcentage of communications that had no answers.
There were not esily noticeable as very small number. But this was abnormal since the application seemed to live good without them.
It could be a bug in Spider!
And it was... or only part of!
Bug seems to be in Redis!
Here is the story of the troubleshooting.
On high volume systems, the map reveals too slow, too crowded to be useful.
I decided to add a predefined dashboard to compensate its usage.
But this dashboard grew beyond my initial thoughts 馃槄, because it already revealed pretty useful!
Even this first official release includes lots of goodies 馃ぉ!
In production we got a use case when searching for records without responses was important.
That was not easy out of the box and required typing in the free search input in Spider.
To ease our lives, I added the feature to have 'missing' option in some filters drop down.
Patrice L. showed me that when there was too may actors in the sequence diagram, the headers were on top on of another, and it was impossible to identify them.
I thus added a feature to highlight and move to the top the header of the lifeline under the mouse.
J茅r茅my M mentioned to me recently that this documentation was missing a search feature.
Here it comes!
After a short poll with users, I've added cURL export to HTTP communications panel.
I just added a link to the original URL of HTTP communication.
It was... missing, really!
An idea to limit memory usage of Redis.
The killer feature that will make me change current training material and a big part of the documentation! 馃槻
This was done in order to simplify usage of Spider.