Skip to main content

Displaying clients on map

· One min read

This week brings several improvements in how clients are displayed on map:

Specific color for clients​

Clients are now display in a yellow/golden color to be visually different from the servers' blue. As for the servers, the golden color is shifting to the red depending of the percentage of errors.

Show list of identifications in client tooltip (HTTP view)​

All identifications used by a client are listed in the Node tooltip on the map (up to 20).

Name clients based their identification (HTTP view)​

Clients that have only one 'identification' are displayed with their identification when their is no DNS name associated to the client. This name is compacted using a regular expression that can be customized in the settings panel.

Move clients to an external ring (option)​

When activated, a ring is drawn outside the server cluster, and all clients are migrated to it to clear the view.

Filter on Aggregated replicas

· One min read

You may know had filter to aggregated replicas directly from the filters list. Previously, it was only possible to do this on the map, and you could not selected several of them.

Do you want to see all instances of this and that server? This is for you!

Fixed concurrency issue

· One min read

Last week I fixed what I hope is the last concurrency issue on the backend real time processing.

Some times (< 100 per day), a first version of an HTTP communication was serialized in ES after the complete version had been. This lead to HTTP communications without response for instance... however the TCP session was parsed correctly and included all packets.

I added version control in Elasticsearch, and this time is over :-)

Global settings tab

· One min read

A new global settings tab has appeared. Its role is to gather and offer change on the configurable processes of the UI. For now:

  • Automatic data refresh
  • Automatic Whisperer status refresh
  • Merging replicas pattern

Improved back end processing

· One min read

I had hard time doing so, but I analysed all logs (Warnings, Errors) from the backend processing.

I then solved a few bugs, corrected a concurrency issue on pollers, and reached a point when:

  • There is less processing :)
  • There is no more Warning / Errors in logs on standard load
  • And: the non regression tests are valid ;)
  • I also fixed some bugs in the meantime on the UI that cause no timeline refresh (but there are still some, for sure ;) )

I'll check tomorrow on a standard loaded day how it behaves.

Merge replicas now applies to Sequence Diagrams

· One min read

Merge Replicas feature is now also applied on sequence diagrams: all replicas of same application are merge on one actor. The effect is as appreciated as for the map: more meaningful information, less noise.

I also added tooltips to sequence diagrams actors (and open action).

Prevent unwanted user selection

· One min read

When trying to drag nodes or timeline selection with a touchpad, or even sometimes with the mouse, many struggled and activated text selection. That caused nuts on the UI.

I added special CSS stuff to prevent selection on the map, tooltips, timeline and so on. This should be much better.

Example: A Ctrl+A on Grid view.

Quick filters on HTTP map for statusCodes

· One min read

Because it was requiring too many clicks, I added a quick filter feature in the tooltips of the HTTP map: -> Want to see what are the 32 requests with 500 status? Just click ! :)

A link is still missing for request without responses. I'll add it soon!