Some of the background information can be found in these pages:

This page will describe in general the layout of the Tools monitor page (aka Admin status page) that displays the number of tools deployed, their location, load and other parameters that enables admin to monitor the health of the system. We shall also discuss about these:
  • How to obtain data from Mongo?
    • Can use Ajax calls to API or controllers
    • TODO: Write API / Controller for getting this information BD-972 - Getting issue details... STATUS
  • Where will this information be rendered?
    • Option 1: Tools Catalog?
      • If we are to do this, we would need to store Elasticity module's Mongo DB somewhere within Tools catalog. Thus Tools catalog will be able to  
      • TODO: Store Elasticity module's MongoDB database details in Tools Catalog
    • Option 2: Another web application?
  • What will be the organization of the information?
    • Option 1: Read Only
      • Main Page
        • Will display the list of tools and high level status details including, tool name, queue name, number of running instances, others if any...
        • TODO: Create Tools Monitor Main page  BD-973 - Getting issue details... STATUS
      • Details Page
        • Will display a selected tool in detail with information like:
          • Running VM instances (IP Address, vCPUs, average load, Docker / VM)
          • Tool description (RabbitMQ queue name, Type, Level, Deployments, Author, URL) or we can just provide a URL to the Tools catalog page.
          • Any other relevant information?
        • TODO: Create Tools Detail page  BD-974 - Getting issue details... STATUS
        • TODO: If required add any other data into MongoDB
    • Option 2
      • Interactive
      • Is this needed?
  • General architecture of the monitoring module and its components

Design Templates


  • No labels