Public Monitoring Sample Clauses

Public Monitoring. ‌ Slice monitoring as described in D3.2 [18] is used to collect and aggregate monitoring data from resources and slices. That data, such as bandwidth measurement and cpu load, is used both for slice provisioning and offering status monitoring to the user once a slice has been setup. The monitoring data is time stamped and stored in one or more databases and aggregate as well as exchanged between several master monitoring systems (e.g., one in Japan and one in Europe). Apart from slice monitoring, we want to provide on the public web site of XXXXX an overview of available infrastructure, that is, connectivity and computing resources, and this with live status updates. The goal of the public monitoring application is to collect data for this overview. This data is mostly status information as retrieved from the Resource Manager components, and possibly resource-specific measurements for infrastructure that is not managed by an RM (for example, ping results on support servers such as DNS, VPN). Unlike slice monitoring, this data is not directly monitored from the resources (such as switches, virtualisation servers), which is why the public monitoring application is a stand-alone tool not dependent on the slice monitoring infrastructure. Since the volume of monitoring data and status information is minimal, public monitoring is performed in a centralised manner and does not need aggregation.
Sample 1
AutoNDA by SimpleDocs
Public Monitoring. ‌ The public monitoring web page gathers connectivity and resource status information from several sources and provides a per-island overview. Only a single instance needs to be deployed, although alternative deployments with a different url and/or configuration are of course possible
Sample 1
Public Monitoring. ‌ Public Monitoring includes basic status information about the facility, such as whether the servers and the net- work connectivity are working as expected. This information is generally available within the stack in each domain (i.e. obtained through some of the exposed APIs of the different RMs). The source for Public Monitoring is available in the GitHub public repository, under the monitoring branch in a folder named public. The configuration step consists on copying the localsettings.py.EXAMPLE into localset- tings.py and filling with the appropriate access data to contact the private APIs on the required RMs. Unlike the Monitoring System, the data is not directly monitored from the resources, which is why the Public Monitoring is a standalone component not dependent on the Monitoring System and it does not need to be deployed on each XXXXX island. Since the volume of monitoring data and status information is minimal, Public Monitoring is performed and deployed in a centralised manner, from where is linked to the XXXXX website to permit public access. The Pub- lic Monitoring tool runs at the iMinds facilities (xxxx://000.000.000.000:0000/xxxxxx/<island_name>), where it periodically polls specific APIs on the different CRM and SDNRM modules that are deployed the moni- tored domains. This enables retrieving topology and availability information on some of the hardware provided by each domain.
Sample 1
Public Monitoring. ‌ Inside the Public Monitoring (or Facility Monitoring), we divided the tasks it performs in two, according to their scope: • Testing availability of soGware modules • Testing connectivity of hardware devices The first one is covered by the First-Level Support site used at Fed4FIRE [5]. This has been possible aGer due integration with the XXXXX XX modules. Finally, the second check is performed within the Public Monitoring tool, which provides status and other detailed information in the form of a separate, public website.
Sample 1
Public Monitoring. ‌ Similar to jFed, the public monitoring system is a tool to allow experimenters check the status of the AMs of the different islands in order to know their availability for the experiment. Once validated that the tool works correctly, the public monitoring system can be, and has been, used as a validation tool since it keeps performs periodic connectivity and login tests and keeps logs of each test. These logs include for each method call its request and response XML RSpecs, making it a very useful tool to check why an RM has failed.
Sample 1

Related to Public Monitoring

  • System Monitoring to ensure safe and continuous operation, the Customer must monitor key services and resource use as recommended by Deswik, and provide Deswik with details of monitoring and any relevant alerts as needed. Services to be monitors include, without limitation, disk space, CPU usage, memory usage, database connectivity, and network utilization.

  • Call monitoring We may occasionally monitor and record calls made to or by us relating to customer services and telemarketing calls made by us, for the purpose of training and improving customer care services, including complaint handling. We and/or our suppliers may also record 999 and 112 calls.

  • Service Monitoring Customer gives express consent for Vodafone to monitor Customer’s use of the Service (and disclose and otherwise use the information obtained) only to: (a) the extent allowed by Applicable Law; (b) comply with Applicable Law; (c) protect the Network from misuse; (d) protect the integrity of the public internet and/or Vodafone’s systems and Networks; (e) the extent necessary to determine if Customer has breached any conditions or restrictions on use of the Service; (f) provide the Service; and/or (g) take other actions agreed or requested by Customer.

  • External monitoring The external monitoring and audit referred to in Articles 11.1, 11.2, 11.3 and 11.4 of the Regulation shall not in any way relieve the National Focal Point or the Programme Operator of their obligations under the legal framework regarding monitoring of the Programme and/or its projects, financial control and audit.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Financial Monitoring City staff shall monitor, review, and evaluate the financial procedures of the Subrecipient through documents submitted to the City and on-site monitoring. The Subrecipient shall provide and make available to the City such reports and records that will be necessary for a proper financial evaluation. With reasonable notice being given to the Subrecipient, the City may schedule at least one on-site visit and other visits that may be needed during the course of this Agreement.

  • Monitoring In each case in which the Foreign Custody Manager maintains Foreign Assets with an Eligible Foreign Custodian selected by the Foreign Custody Manager, the Foreign Custody Manager shall establish a system to monitor (i) the appropriateness of maintaining the Foreign Assets with such Eligible Foreign Custodian and (ii) the contract governing the custody arrangements established by the Foreign Custody Manager with the Eligible Foreign Custodian. In the event the Foreign Custody Manager determines that the custody arrangements with an Eligible Foreign Custodian it has selected are no longer appropriate, the Foreign Custody Manager shall notify the Board in accordance with Section 3.2.5 hereunder.

  • Compliance Monitoring Grantee must be subject to compliance monitoring during the period of performance in which funds are Expended and up to three years following the closeout of all funds. In order to assure that the program can be adequately monitored, the following is required of Grantee:

  • EVALUATION AND MONITORING The ORGANIZATION agrees to maintain books, records and other documents and evidence, and to use accounting procedures and practices that sufficiently and properly support the complete performance of and the full compliance with this Agreement. The ORGANIZATION will retain these supporting books, records, documents and other materials for at least three (3) calendar years following the year in which the Agreement expires. The COUNTY and/or the State Auditor and any of their representatives shall have full and complete access to these books, records and other documents and evidence retained by the ORGANIZATION respecting all matters covered in and under this Agreement, and shall have the right to examine such during normal business hours as often as the COUNTY and/or the State Auditor may deem necessary. Such representatives shall be permitted to audit, examine and make excerpts or transcripts from such records, and to make audits of all contracts, invoices, materials, and records of matters covered by this Agreement. These access and examination rights shall last for three calendar years following the year in which the Agreement expires. The COUNTY intends without guarantee for its agents to use reasonable security procedures and protections to assure that related records and documents provided by the ORGANIZATION are not erroneously disclosed to third parties. The COUNTY will, however, disclose or make this material available to those authorized by/in the above paragraph or permitted under the provisions of Chapter 42.56 RCW without notice to the ORGANIZATION. The ORGANIZATION shall cooperate with and freely participate in any other monitoring or evaluation activities pertinent to this Agreement that the COUNTY finds needing to be conducted.

Time is Money Join Law Insider Premium to draft better contracts faster.