PROC06 Setting Nagios test status to operations

From EGIWiki
(Redirected from PROC06)
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators




Title Setting Nagios test status to operations
Document link https://wiki.egi.eu/wiki/PROC06
Last modified 2020-03-02
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations@egi.eu
Document Status Approved
Approved Date 2020-02-20
Procedure Statement The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for including Nagios tests into the ARGO_MON_OPERATORS profile: in this way, the operations dashboard will display an alarm in case the test fails.
Owner Alessandro Paolini


Overview

The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for including Nagios tests into the ARGO_MON_OPERATORS profile: in this way, the operations dashboard will display an alarm in case the test fails.

This procedure only applies for tests run under OPS VO and its range is global, applies for all Operations Centres in EGI project.


Definitions

Please refer to the EGI Glossary for the definitions of the terms used in this procedure.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.


Steps

Prerequisites

The ARGO test needs to meet the following requirements.

  1. It satisfies quality criteria in agreement with the UMD operational capabilities quality criteria: https://documents.egi.eu/document/240.
  2. It is properly documented.
  3. It must be part of an official nagios release.
  4. It must have been deployed in production for at least one month without problems.
  5. It must be available for validation by Operations

Sending a request

  • Anybody can submit the request for making the test an operations test.
  • The request should be submitted to Operations via a GGUS ticket.

Validation

Step Action on Action
1 Applicant Opens a GGUS ticket to Operations to start the process.
Subject: Request for setting XXX test an operations test

Dear Operations,

We would like to request for setting XXX test an operations test

Prerequisite data:
* name of nagios probe:
* name of service on which the test runs: 
* link to documentation page:
* motivation (which part of the infrastructure will be improved by making XXX test 
 or description of users' problems which will be avoided in future - provide list 
 of GGUS tickets is possible)

Best Regards
XXX
2 Operations Checks the status of the Nagios probe to see if it meets the specified quality criteria.
3 Operations Operations contacts the OMB to request the approval of the new operations test. Date is specified (at least 1 month in future)
4 NGIs Request to the ROD teams to try making the test OK. 75% OK in total (entire EGI) is understood as threshold for passing to the next step. If not possible to proceed, report problems to OMB.
5 Operations Reassigns the ticket to "Monitoring (ARGO)" agreeing on the date for the inclusion of the test in the operations profile
6 Operations The announcement about the new operations test is Monthly broadcast 

(This broadcast should be sent to site managers, NGI managers and ROD teams) See the template below for an indication of the message content.

Subject: XXX have been added to the EGI Operations Profile on XXX 

Dear All,

We would like to announce that test XXX will become operational on XXX

Short description of the test:

The documentation can be found:

Best regards,
7 Operations Final check. Close parent ticket


Revision history

Version Authors Date Comments
M. Krakowian 19 August 2014 Change contact group -> Operations support
Alessandro Paolini 2016-06-08 "EGI Operations Support" was decommissioned, changed all the references to "Operations"
Alessandro Paolini 2019-02-25 updated some old acronyms; removed the step 7 where ARGO team had to modify the related POEM profile; added the link to the operations portal in the step 6
Alessandro Paolini 2019-12-17 updated steps 5 and 6, since the operations tests are managed on Poem (ARGO_MON_OPERATORS) by ARGO team, no more through the operations dashboard