The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Regionalized Nagios use cases"
| Line 11: | Line 11: | ||
==Use cases== | ==Use cases== | ||
===Use case #1=== | ===Use case #1=== | ||
Monitor sites and service not in central gocdb. | |||
====Use case description==== | ====Use case description==== | ||
NGIs could need to monitor sites not in the central gocdb, test sites or sites not in EGI because founded separately. | |||
====Dependencies with other regionalized tools==== | ====Dependencies with other regionalized tools==== | ||
regionalized GOCDB, custom ATP | |||
<!-- end use case block --> | <!-- end use case block --> | ||
===Use case #2=== | |||
====Use case description==== | |||
====Dependencies with other regionalized tools==== | |||
<!-- end use case block --> | |||
[[Category:Tools]] | [[Category:Tools]] | ||
Revision as of 12:06, 24 March 2011
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Current status of regionalization
Nagios/SAM provides regionalized version which is synchronized with the central instance. SAM/Nagios releases follow EGI software release process. List of NGI instances can be found on the following page: SAM Instances.
ATPs at NGI instances are independent from the central one, meaning that they perform synchronization with information sources directly. NGI instance could in theory point ATP to different information sources (e.g. alternative VO feeds).
Use cases
Use case #1
Monitor sites and service not in central gocdb.
Use case description
NGIs could need to monitor sites not in the central gocdb, test sites or sites not in EGI because founded separately.
Dependencies with other regionalized tools
regionalized GOCDB, custom ATP