PROC07 Adding new probes to SAM

From EGIWiki
(Redirected from PROC07)
Jump to: navigation, search
Main 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 Adding new probes to SAM
Document link
Last modified 8 June 2016
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group
Document Status Approved
Approved Date 28 March 2010
Procedure Statement This document specifies the procedure for adding new probes to the ARGO-SAM release.


The purpose of this document is to clearly describe the procedure for adding new Nagios probes to the ARGO-SAM release.


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.

The key words Metric, Probe are defined in the following way:


This procedure only applies to probes which are run under OPS VO and whose scope is global. The implication of this is that any change requested through this procedure has an impact on all EGI Operations Centres in EGI.

This procedure does not apply to SAM internal probes which perform monitoring of individual components on the ARGO-SAM instance (e.g. process monitoring, ActiveMQ connections, etc.).

Entities involved in the procedure


Step Action on Action
1 Applicant A request is submitted through a EGI GGUS ticket (https:/ by assigning to Operations SU.
Subject: Request for adding new probe XXX to ARGO-SAM

We would like to request adding new probe XXX to ARGO-SAM release

Prerequisite data:
* name of the Nagios probe:
* name of service on which the test runs:
* link to documentation page:
* motivation (which part of the infrastructure will be improved with the new probe
 or description of users' problems which will be avoided in future - provide list
 of GGUS tickets is possible)
2 COO Reviews the requirement submitted, and schedules a presentation of the new probe at the next possible OMB meeting.
3 Applicant Presents the new probe.
4 OMB OMB decides if the new probe will be included in the SAM. The next steps are performed only if the probe is accepted.
5 ARGO-SAM Product Team The SAM Product Team defines schedule for including the new probe into a ARGO-SAM release.
6 Applicant, ARGO-SAM Product Team The probe integration process is performed.
7 ARGO-SAM Product Team Add the description of the new probe and tests it provides to section "New tests" of the Release notes of ARGO-SAM release which contains the new probe.
8 COO Closes the initial GGUS ticket.

Revision History

Version Authors Date Comments
M. Krakowian 2014-08-19 Changed contact group -> Operations support
C. Aiftimiei 2014-09-18 Removed broken link "detailed description" on Step 6
Alessandro Paolini 2016-06-08 Changed contact group -> Operations
Alessandro Paolini 2017-06-01 Changed the name SAM to ARGO-SAM
Alessandro Paolini 2018-06-19 Definitions: Metric and Probed as defined in the deprecated terminology page (link removed). Overview: updated the link to ARGO/SAM wiki page
Personal tools