1 / 11

SUM like functionality with WLCG-MON Ivan Dzhunov

SUM like functionality with WLCG-MON Ivan Dzhunov. What do we mean by SUM like?. Historical plots sites availability/reliability s ervices availability/reliability metrics history per hostname metric’s detailed output Latest results table “SUM uses the screen very economically”

manjit
Download Presentation

SUM like functionality with WLCG-MON Ivan Dzhunov

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SUM like functionality with WLCG-MON Ivan Dzhunov

  2. What do we mean by SUM like? • Historical plots • sites availability/reliability • services availability/reliability • metrics history per hostname • metric’s detailed output • Latest results table • “SUM uses the screen very economically” • drill down navigation between the plots • filters for sites, group of sites, services, metrics, hostnames Ivan Dzhunov

  3. Site reliability historical plot • New type of historical metric plot implemented in SSB (WLCG-MON) • Reliability calculated by formula good/(good+bad) • good = {‘warning’, ‘ok’} • bad = {‘critical’, ‘unknown’} • Configurable per metric • Idea is to use the same plot for service reliability Ivan Dzhunov

  4. Service reliability historical plot ? • We need plot like showing reliability for set of service flavors (CREAM-CE, SRMv2) for set of sites (T2_ES_CIEMAT, T2_FR_CCIN2P3) per profile • In SSB status of single service flavor (per profile) is different metric • Need of cross metric, cross instance historical SSB plot – MxN • SSB not flexible enough, has historical plots only per metric (1xN) or per instance (Mx1) • Here we thought a bit. If we want to provide SUM like functionality, why not use SUM ? Ivan Dzhunov

  5. Current usage of SUM API calls SAM data SUM UI get current data SSB UI SSB data • SUM • User interface for displaying SAM data • No DB behind it, works with API calls • SSB interacting with SUM • SSB data not in sync with re-computed historical SAM data Ivan Dzhunov

  6. Future usage of SUM API calls SUM UI topology WLCG-MON profile definition metric results SSB UI • SUM on top of WLCG-MON • Single data store • Re-computed data will be seen by both applications Ivan Dzhunov

  7. SUM on top of WLCG-MON http://wlcg-sam-cms.cern.ch Ivan Dzhunov

  8. Advantages of using SUM • Migration to WLCG-MON will be transparent for the end user • SUM will serve the same plots and data as it used to do • No UI has to be re-written • Validation of the new system will be much easier • Validate data out of two equivalent systems – “old” and “new” SUM Ivan Dzhunov

  9. Disadvantages of using SUM Maintain 2 different user interfaces Ivan Dzhunov

  10. Which way do we go ? Ivan Dzhunov

  11. WLCG-MON TODO list …assuming we decide to adopt SUM • SUM side • metric result details and latest results part • Availability plots when site/service downtimes are introduced to WLCG-MON • Profiles definition – currently in static JSON file -> move to DB • Changes in aggregation, SUM actions • Service type <-> flavor mapping • Changes in aggregation?, SUM actions • Site/service downtime handling • Re-computations on aggregated data with SSB “modify metric data” functionality • Validate data • Monthly reports Ivan Dzhunov

More Related