1 / 13

Enhancing Service Status Monitoring with SSB Aggregation

This document outlines the SSB (Service Status Board) Aggregation system, designed to simplify service monitoring by reducing the scope of service, minimizing effort, and maximizing reuse. Utilizing SSB virtual metrics, the system computes service/site status across diverse metrics, including Nagios probes. It proposes a generic, data-agnostic aggregation strategy, ensuring seamless integration with existing services and metrics. Key elements include a flexible topology, independent FQANs, and a focus on profile definition and algorithm optimization, all while addressing current limitations and challenges.

lexi
Télécharger la présentation

Enhancing Service Status Monitoring with SSB Aggregation

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. Service and Site statusthroughSSB Aggregation Jacobo Tarragón IT/SDC November 8th, 2013

  2. motivation • simplify service monitoring • reduced SAM scope • reduced effort • reuse as much as possible • aggregation maps nicely to SSB virtual metrics SSB Aggregation

  3. motivation use SSB virtual metrics to compute service/site status from any metric, including Nagios probes SSB Aggregation

  4. strategy • generic aggregation system • using SSB metrics • data agnostic • POEM–like profile definition • metrics and FQANs • algorithm SSB Aggregation

  5. profile definition Translates to 5 aggregation metrics: CMS_CRITICAL (service CE) aggregates CE metrics per service CMS_CRITICAL (service SRM) aggregates SRM metrics per service CMS_CRITICAL (CE) aggregates CE services per site CMS_CRITICAL (SRM) aggregates SRM services per site CMS_CRITICAL combines CE and SRM site results { "name": "CMS_CRITICAL”, "algorithm": "CE * SRM", "metric_instances": [ { "atp_service_type_flavour": "CE", "fqan": "/cms/Role_production", "metric": "org.sam.CREAMCE-JobSubmit" }, { "atp_service_type_flavour": "CE", "fqan": "/cms/Role_lcgadmin", "metric": "org.sam.CREAMCE-JobSubmit" },…, { "atp_service_type_flavour": "SRM", "fqan": "/cms/Role_production", "metric": "org.cms.SRM-GetPFNFromTFC" }, { "atp_service_type_flavour": "SRM", "fqan": "/cms/Role_production", "metric": "org.cms.SRM-VOGet" },…, ], "service_site_metric": "cms topology (site)" } SSB Aggregation

  6. simplified algorithms (ARC–CE + OSG–CE + CE + CREAM–CE) + (SRMv2 + OSG–SRMv2) vs. CE + SRM • when different flavours have the same metrics, they can be simplified • flavour names are arbitrary • just a way to group metrics! • makes aggregation faster • but eliminates flavour status SSB Aggregation

  7. FQAN support Metric results with different FQANs grouped (introduces additional aggregations): (CE_prod + CE_lcgadmin) * (SRM_prod + SRM_lcgadmin) { "atp_service_type_flavour": "CE_prod", "fqan": "/cms/Role_production", "metric": "org.sam.CREAMCE-JobSubmit" }, { "atp_service_type_flavour": "CE_lcgadmin", "fqan": "/cms/Role_lcgadmin", "metric": "org.sam.CREAMCE-JobSubmit" }, Metric results with different FQANs mixed: CE * SRM { "atp_service_type_flavour": "CE", "fqan": "/cms/Role_production", "metric": "org.sam.CREAMCE-JobSubmit" }, { "atp_service_type_flavour": "CE", "fqan": "/cms/Role_lcgadmin", "metric": "org.sam.CREAMCE-JobSubmit" }, each metric + FQAN is independent FQANs may be grouped in flavours SSB Aggregation

  8. topology • VO feed as only source • not limited to services in GOCDB • stored as regular metrics in SSB • metric results are not filtered • every tested endpoint in the topology will be aggregated SSB Aggregation

  9. current limitations • no downtime support • will be implemented using service/site downtime metrics • mixed service flavour instances • CREAM–CE aggregation considers ARC–CE services when same metrics are used • a topology filter will be implemented SSB Aggregation

  10. metric validity • SAM metrics have 24h validity • shorter validity means closer to real–time • but metric results are not always regular! SSB Aggregation

  11. upcoming challenges • filters • selective aggregation of services • profiles for arbitrary topology subsets • availability and reliability • applicable to any SSB metric • downtimes needed • validation • both local and with MRS/ACE SSB Aggregation

  12. summary of key changes • flexible topology • everything in the VO feed • data agnostic • flavours are arbitrary • source metrics can be anything in SSB • independent FQANs • but they can still be aggregated • profile and algorithm definitions • POEM integration to be discussed SSB Aggregation

  13. demo http://wlcg-mon.cern.ch SSB Aggregation

More Related