Difference between revisions of "Procedure Infrastructure Monitoring"

From D4Science Wiki
Jump to: navigation, search
(→‎gCube Resources)
Line 1: Line 1:
−
__NOTOC__
+
__TOC__
−
The monitoring of the D4Science Ecosystem is carried out by [[Role Infrastructure Manager|Infrastructure Managers]], [[Role Site Manager|Site Managers]], [[Role VRE Manager|VRE Managers]], [[Role VO Admin|VO Admins]], and [[Role Data Manager|Data Managers]]. Such activity is done on a regular basis using the different tools provided to monitor the status of gCube , gLite, Hadoop and Runtime Resources (check below).
+
 
 +
== D4Science Infrastructure Monitoring ==
 +
 
 +
The monitoring of the D4Science infrastructure is carried out by [[Role Infrastructure Manager|Infrastructure Managers]], [[Role Site Manager|Site Managers]], [[Role VRE Manager|VRE Managers]], [[Role VO Admin|VO Admins]], and [[Role Data Manager|Data Managers]]. Such activity is done on a regular basis using the different tools provided to monitor the status of the Resources (check below).
  
 
In case a new problem is identified an incident should be reported immediately following the [[Procedure Infrastructure Incident Management|Incident Management]] procedure.
 
In case a new problem is identified an incident should be reported immediately following the [[Procedure Infrastructure Incident Management|Incident Management]] procedure.
  
  
−
== gCube Resources ==
+
== D4Science Resources ==
  
−
The monitoring of the gCube Resources of the infrastructure is based on several systems:
+
The monitoring of the D4Science Resources of the infrastructure is based on several systems:
  
 
* IS Monitoring: Based on information published in the gCube Information System. This information is accessible from:  
 
* IS Monitoring: Based on information published in the gCube Information System. This information is accessible from:  
−
** [http://monitor.d4science.research-infrastructures.eu/rm Advanced Monitoring]
+
** [https://services.d4science.org/group/d4science.research-infrastructures.eu/accounting Advanced Monitoring]
 
* Messaging System: Based on the information published by probes local to each node. This information is used to send emails to [[Role Site Manager|Site Managers]] when problems are found.
 
* Messaging System: Based on the information published by probes local to each node. This information is used to send emails to [[Role Site Manager|Site Managers]] when problems are found.
−
* Nagios: Based on the information gathered by [http://www.nagios.org/ Nagios] about the availability of each gHN. In case of problems Nagios notifies by mail the [[Role Infrastructure Manager|Infrastructure Managers]].  The iMarine Data e-Infrastructure Nagios server is available at [https://nagios.d4science.org:8443/nagios/ Nagios Server]
+
* Nagios: Based on the information gathered by [http://www.nagios.org/ Nagios] about the availability of each gHN. In case of problems Nagios notifies by mail the [[Role Infrastructure Manager|Infrastructure Managers]].  The D4Science Nagios server is available at [https://nagios.d4science.org/nagios/ Nagios Server]
−
* Ganglia: Based on the information gathered by [http://ganglia.sourceforge.net/ Ganglia] server contacting a series of agents deployed on the infrastructure nodes. The iMarine Data e-Infrastructure Ganglia server is available at [https://imarine1.cern.ch/ganglia/ Ganglia Server]
+
−
 
+
−
== UMD Resources ==
+
−
 
+
−
There are several tools to monitor the EGI production infrastructure resources and consequently the UMD resources. Many of these tools share the same information source providing only different views over it. Such large number of tools cover many monitoring possibilities.
+
−
 
+
−
* Services Availability: [http://gridview.cern.ch/GRIDVIEW/dt_index.php GridView], [https://grid-monitoring.egi.eu/myegi MyEGI]
+
−
* Services Status: [http://gstat.egi.eu/gstat/geo/openlayers GStat], [http://gridportal.hep.ph.ic.ac.uk/rtm RTM]
+
−
* Services Information: [http://goc.egi.eu/ GOCBD]
+
−
 
+
−
The table below provides direct links to status of the different UMD sites of the infrastructure provided by iMarine members:
+
−
 
+
−
{| border="1" cellpadding="4" cellspacing="0"
+
−
|-
+
−
! width="60"| !! width="100" |Site !!  width="200" |Service Availability
+
−
|-
+
−
| bgcolor="lightgrey" align="center"|CNR || [https://goc.egi.eu/portal/index.php?Page_Type=View_Object&object_id=164&grid_id=0 gocdb]  [http://goc.grid.sinica.edu.tw/gstat/CNR-PROD-PISA gstat] || [https://grid-monitoring.egi.eu/myegi/sa/?view=3&facelist_values_groups=&vo=37&profile=15&site=375&graph=1 MyEGI Service Availability]
+
−
|-
+
−
| bgcolor="lightgrey" align="center"|NKUA || [https://goc.egi.eu/portal/index.php?Page_Type=View_Object&object_id=261&grid_id=0 gocdb] [http://goc.grid.sinica.edu.tw/gstat/GR-09-UoA gstat] || [https://grid-monitoring.egi.eu/myegi/sa/?view=3&facelist_values_groups=&vo=37&profile=15&site=337&graph=1 MyEGI Service Availability]
+
−
|}
+
  
  
 
== Hadoop Resources ==
 
== Hadoop Resources ==
  
−
The Hadoop clusters are monitored trough the Hadoop internal monitoring and tracking systems. These tools provide monitoring for [http://hadoop.apache.org/mapreduce/ MapReduce] jobs and for [http://hadoop.apache.org/hdfs/ HDFS] filesystems.
+
The Hadoop clusters are monitored through the Hadoop internal monitoring and tracking systems. These tools provide monitoring for [http://hadoop.apache.org/mapreduce/ MapReduce] jobs and for [http://hadoop.apache.org/hdfs/ HDFS] filesystems.
  
 
{| border="1" cellpadding="4" cellspacing="0"  
 
{| border="1" cellpadding="4" cellspacing="0"  
Line 51: Line 34:
  
 
* IS Monitoring: Based on information published in the gCube Information System. This information is accessible from:  
 
* IS Monitoring: Based on information published in the gCube Information System. This information is accessible from:  
−
** [http://monitor.d4science.research-infrastructures.eu/rm Advanced Monitoring]
+
** [https://services.d4science.org/group/d4science.research-infrastructures.eu/accounting Advanced Monitoring]
−
* Nagios: Based on the information gathered by [http://www.nagios.org/ Nagios] about the availability of each Runtime Resource. For some of the Runtime Resources additional checks are going to be instrumunted ( e.g. Mysql or PSQL DB DB sizes, or Index Usages) in Nagios.In case of problems Nagios notifies by mail the [[Role Infrastructure Manager|Infrastructure Managers]]. The iMarine Data e-Infrastructure Nagios server is available at [https://nagios.d4science.org:8443/nagios/ Nagios Server]
+
* Nagios: Based on the information gathered by [http://www.nagios.org/ Nagios] about the availability of each Runtime Resource. For some of the Runtime Resources additional checks are going to be instrumented ( e.g. Mysql or PSQL DB DB sizes, or Index Usages) in Nagios.In case of problems Nagios notifies by mail the [[Role Infrastructure Manager|Infrastructure Managers]]. The iMarine Data e-Infrastructure Nagios server is available at [https://nagios.d4science.org/nagios/ Nagios Server]

Revision as of 19:22, 27 March 2018

D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Infrastructure Monitoring

The monitoring of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. infrastructure is carried out by Infrastructure Managers, Site Managers, VRE Managers, VO Admins, and Data Managers. Such activity is done on a regular basis using the different tools provided to monitor the status of the Resources (check below).

In case a new problem is identified an incident should be reported immediately following the Incident Management procedure.


D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Resources

The monitoring of the D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Resources of the infrastructure is based on several systems:

  • IS Monitoring: Based on information published in the gCube Information System. This information is accessible from:
  • Messaging System: Based on the information published by probes local to each node. This information is used to send emails to Site Managers when problems are found.
  • Nagios: Based on the information gathered by Nagios about the availability of each gHN. In case of problems Nagios notifies by mail the Infrastructure Managers. The D4ScienceAn e-Infrastructure operated by the D4Science.org initiative. Nagios server is available at Nagios Server


Hadoop Resources

The Hadoop clusters are monitored through the Hadoop internal monitoring and tracking systems. These tools provide monitoring for MapReduce jobs and for HDFS filesystems.

MapReduce HDFS
CNR
Job Tracker
DFS Health

Runtime Resources

The monitoring of the Runtime Resources of the infrastructure is based on 2 systems:

  • IS Monitoring: Based on information published in the gCube Information System. This information is accessible from:
  • Nagios: Based on the information gathered by Nagios about the availability of each Runtime Resource. For some of the Runtime Resources additional checks are going to be instrumented ( e.g. Mysql or PSQL DB DB sizes, or Index Usages) in Nagios.In case of problems Nagios notifies by mail the Infrastructure Managers. The iMarine Data e-InfrastructureAn operational combination of digital technologies (hardware and software), resources (data and services), communications (protocols, access rights and networks), and the people and organizational structures needed to support research efforts and collaboration in the large. Nagios server is available at Nagios Server
Retrieved from "https://wiki.d4science.org/index.php?title=Procedure_Infrastructure_Monitoring&oldid=21698"