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 "Nagios requirements"
(Created page with '= Submitting a Nagios test requirement = NGI/EIRO Operations Centre Managers can submit Nagios probe requirements on behalf of their NGI and their resource centres. Requirements…') |
|||
| Line 61: | Line 61: | ||
* '''Grid service that should be test.''' | * '''Grid service that should be test.''' | ||
** Which metric the probe should return | ** Which metric the probe should return | ||
* '''Write a brief description of the probe.''' | * '''Write a brief description of the probe.''' | ||
** Specify a use case if possible. | ** Specify a use case if possible. | ||
* '''Is NGI prepared to develop probes?''' | * '''Is NGI prepared to develop probes?''' | ||
Revision as of 16:38, 11 January 2011
Submitting a Nagios test requirement
NGI/EIRO Operations Centre Managers can submit Nagios probe requirements on behalf of their NGI and their resource centres. Requirements are collected on the requirements hosted on the EGI RT system.
Who is authorized to open a ticket?
NGI/EIRO Operations Centre Managers that are members of the noc-managers SSO group and SA1 task leaders.
Opening a ticket on RT
Go to RT, select the requirements queue (top right-hand corner) from the drop-down menu, and select New ticket.
Setting a Nagios probe requirement ticket
- Owner: Daniele Cesini
- Category (leve 1): "Unified Middleware Distribution"
- Category (level 2): "Monitoring"
- Category (level 3): "no value"
- Requestor (level 1): "NGI or EIRO"
- Requetor (level 2): select your NGI, or Other in case your NGI does not appear in the drop down menu
- Reqiestor (level 3): "no value"
- Technology Tag: select the specific middleware distribution if relevant, or specify "no value" if the requirement is applicable to all stacks
- Custom Tag: "new nagios probe1/modify nagios probe2/request nagios probe3"
1In case of a Category 1 requirement
2In case of a Category 2 requirement
3In case of a Category 3 requirement
- Non Functional Tag: select what is applicable from the drop-down menu, depending on the type of requirement
Priority
Nagios test requirement categories
Category 1
Probes developed by NGI to be integrated into SAM. A NGI/EIRO or site manager may have developed an own prove that can be useful to the whole EGI.
Please, for each probe, in the body of the ticket provide the following information:
- Grid service that probe tests.
- Specify which feature of the service is tested by the probe (e.g. CPU load)
- Brief description of test.
- In addiction, put in the description in which case the probe returns 'critical' and when it returns 'warning'.
- Developer contact information
Category 2
Changes to existing probes. An NGI/EIRO can submit a requirement if the test should which tests be done differently. For each probe in the body of the ticket provide the following information:
- Grid service tested
- Test name
- Brief description of changes
- In addition to the description, add a use case as example.
- Is NGI prepared to develop changes?
Category 3
Missing tests. If additional tests should be run, the NGI/EIRO can submit a requirement specifying the test that should be developed. For each probe in the body of the ticket provide the following information:
- Grid service that should be test.
- Which metric the probe should return
- Write a brief description of the probe.
- Specify a use case if possible.
- Is NGI prepared to develop probes?