Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Following on from the work in the October Release where we improved communication with and control of the engine we have focussed on the following areas in this release: 

  • Visual Testing - making this as reliable as we would like 
  • Engine Listener Balancing 

Visual Testing 

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

  • The graph may show the pulsating listener icon but may not show the "Running" confirmation in the testing console
  • The graph may under report the number of events - in some cases not showing any events at all

All of 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 the communication process so that the client will poll a distinct service to get the visual testing results. We believe that this has eradicated all of the visual testing woes that we have seen above. 

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 our configurers. 



The Testing Console will automatically expand the most recent test run and fold up the previous finished runs: 

Transaction Highlighting

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

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

Sub-task

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

  • [KIT-2012] - QA TICKET - Post 1.13.3 Engine Tweaks(KIT-2017)
  • [KIT-2016] - QA TICKET - KIT-2015 Rebalance Less
  • [KIT-2018] - QA TICKET - Engine Visual Trace Logger (KIT-1974)
  • [KIT-2035] - Flask Routes Freezing KIT-2001
  • [KIT-2041] - Graphs in Deployed_Graphs need to show up in graphs route
  • [KIT-2063] - Release testing - Version 1.13.4
  • No labels