1 / 14

IT Monitoring WG Shared Architecture V3

IT Monitoring WG Shared Architecture V3. MWS November 28 2011. Where we are:. Feedback. Quite a bit, but not as much as hoped not all feedback was based on what had been discussed, some was “ freeform ” some feedback posted to the list created a bit confusion

davida
Télécharger la présentation

IT Monitoring WG Shared Architecture V3

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. IT Monitoring WGShared ArchitectureV3 MWS November 28 2011

  2. Where we are: Terminology and Shared Architecture - 2

  3. Feedback • Quite a bit, but not as much as hoped • not all feedback was based on what had been discussed, some was “freeform” • some feedback posted to the list created a bit confusion • The Terminology that had been developed had been partially forgotten.... • First Impression: Terminology and Shared Architecture - 3

  4. Second Impression • Some important input: • Some services depend on end-end (commercial) solution • Application specific storage seen as necessary for high performance analysis • Common Schema is a fearsome thought • Many open questions on the transition/introduction • Flexibility/Pluggable system (I♥ Flexibility) • Where should results of analysis go? • Visualization, common tools/technologies • Suggestions to go for full commercial stack Terminology and Shared Architecture - 4

  5. Some services depend on end-end (commercial) solutions • Problem: Linking with other monitoring data • Possible solutions: • Treating the complete chain as a “Super Sensor” • injecting the results into the transport (messaging layer) • Exporting relevant data at an intermediate stage Visualization/Reports Analysis Storage Aggregation/MessagingQ Transport Sensor Integrated Product Export Interface Terminology and Shared Architecture - 5

  6. Application specific storage • Application specific storage for demanding analysis • Closely related to transition problem and direct feed for Alarms • Messaging Service can feed GUFS/Alarms/Custom storage Portal Portal Analysis Portal Analysis Analysis Tool Tool Tool Alarm Alarm Report Alarm Report Alarm Report Alarm Alarm Custom Feed Aggregation Alarm Feed Scrub Application Specific Sys. Backup Aggregation GUFS Feed Aggregation/Message-Q Broker Broker Submission 1 Submission 2 Submission 3 Terminology and Shared Architecture - 6

  7. Common Schema • Likely too complex + inflexible • Common data format, based on well supported technology • JSON • NOT XML • Question: • How do I know which data exists?? • essential for combining data Terminology and Shared Architecture - 7

  8. transition/introduction • Steps: • Old and new co-exists • Prototypes of core components • Prototypes used by some teams in parallel • new monitoring can go directly • existing sensors can be interfaced • Prototypes  small scale production • some activities move to the new system (first parallel to old system) • Production system is scaled gradually as more components join • old system is gradually phased out Terminology and Shared Architecture - 8

  9. Introduction/Transition Portal Portal Analysis Portal Analysis Analysis Tool Tool Tool Report Report Report NEW Aggregation Broker Broker OLD Submission 1 Submission 2 Submission 3 Terminology and Shared Architecture - 9

  10. Flexible/Pluggable System • Messaging System and GUFS as glue • Keeping Sensors simple • export interface either directly on sensor or after first aggregation • Exporting intermediate analysis results back into Messaging System • to be used by other consumers • Connecting tools either to the Messaging System or GUFS • Common data format • All components can be changed easily • including the message system (standard protocol) Terminology and Shared Architecture - 10

  11. Where should results of the analysis go? • Reports, results from complex analysis should go back into the system • GUFS • Messaging system • Allows others to combine results with their data Terminology and Shared Architecture - 11

  12. Full Commercial Stack • One “does it all” system unlikely to exits • would at least require some work on the sensors • not very flexible, can lead to vendor lock in • this approach had been tried with PVSS • successful, but fitting it in wasn’t for free • We should use commercial tools wherever they make sense • list candidates for the different “layers” • starting with a paper evaluation and prototype use Terminology and Shared Architecture - 12

  13. Visualization, Tools • These are the legs of the elephant in the room • We need to attack this area in the next meetings Analysis Visualization Reports Terminology and Shared Architecture - 13

  14. Other comments.... • There where questions and suggestions on how to proceed • Here I focussed on the Architecture related comments • Next agenda item is about the “next steps” Terminology and Shared Architecture - 14

More Related