Page Comparison

...

• Visual Testing - making this more reliable and easier to use
• Engine Listener Balancing - ensuring that processing of requests happens evenly across the engines

Visual Testing 

Visual testing is an important part of the graph development cycle in the Kitewheel Hub. We had been tracking several issues with visual testing and had seen a number of potential problems: 

...

These issues were caused by a lack of robust communications between the browser and the Kitewheel Hub which meant that a single missed piece of communication could result in the issues above. Essentially this all came down to timing. In order to resolve this we have reversed re-engineered the communication process so that the client will poll a distinct service to get the visual testing results. We believe that this has eradicated the vast majority of visual testing problems. 

Not content with that set of fixes we have also made some changes to the visual display of the visual testing information to make life easier for all Kitewheel configurers. 

Testing Console Transaction Expansion 

The Testing Console will automatically expand the most recent test run and fold up the previous finished runs. This allows you to automatically see the most recent run and makes it easier to navigate to the information that you to automatically need to see if your test was successful.

Transaction Highlighting

The transaction expand arrow and the Transaction Number text will now all highlight to make it easier to see which 

Image Removed

When the test has finished the Listen Started... message will be removed. 

Image Removed

Sub-task

• [KIT-2015] - Rebalance Less
• [KIT-2017] - Rebalanced Listeners Start/Stop change

Bug

• [KIT-1838] - Managed graph schema exposed to end user (long standing regression)
• [KIT-2071] - Org Dropdown Toggle Bug

Epic

• [KIT-1459] - VTS Shows lack of solid communication between engine and hub - Multiple issues arise due to hight traffic and multi-engine/Multi-hub environments

Story

• [KIT-1968] - Update Reporting Service to accept and store visual trace
• [KIT-1969] - Catalog all places where trace data is emitted from and standardize output format
• [KIT-1970] - Create Routes to expose collected trace data
• [KIT-1971] - Add hub backend routes to proxy the metrics service trace data routes
• [KIT-1972] - Modify the front end to use the new trace routes
• [KIT-1973] - Minor front end tweaks to deal with issues
• [KIT-1974] - Modify the engine to work with the new visual trace logger

Task

• [KIT-1368] - Organization Navigation Redesign Implementation
• [KIT-2036] - Return 500 if arbiter key doesn't exist
• [KIT-2044] - Currently gulp is pulled from github directly in our Package.json for Hub we need to fix that
• [KIT-2050] - Add nowait route to graph api
• [KIT-2053] - Implement database storage paradigm and migration for time based metrics
• [KIT-2066] - Create Migration for updating Version Number in Hub

QA Story

...

which transaction is being shown and the path that transaction took will now be highlighted in yellow rather than blue. This makes it easier to follow the path of the transaction. 

Image Added

Image Added

Engine Listeners

Over the last two releases we have put in some effort to get more efficient use of the hardware used for the Kitewheel Engine stack. There are two types of process which run on the engine - the listeners and the job processors. These will be familiar to you from the Kitewheel graph interface. The number of listeners and the amount of work that each listener does can affect the performance of an engine. Prior to this work it was possible for a number of listeners to end up on a single engine processor which caused the stack to become unbalanced. Kitewheel now actively manages the listeners and where possible creates an even balance of listeners across the engine stack. 

This is a small step towards a re-architecture of the Kitewheel engine which will have performance and stability improvements in future releases. Most of these changes will be invisible to the user but should result in faster graph execution times and lower costs to service the same number of graphs. 

Bug Fixes

A number of other bugs were fixed in this release: 

• [KIT-1838] - Managed graph schema exposed to end user - the schema for managed graphs is no longer visible
• [KIT-2035] - Flask routes freezing could cause engine failure 
• [KIT-2071] - Org dropdown - the organisation drop down available to OEM users had a display issue that has now been fixed