Monthly Uptime Measurement Sample Clauses

Monthly Uptime Measurement. The Parties agree SUSE will measure up-time using a third party, up-time monitoring system. Data points will be collected at least once a minute. The endpoint for the Customer’s instance of the SUSE Rancher Software will be queried and must respond within 5 seconds with an HTTP 200 return code to be considered within the SLA. No response, non-HTTP 200 return code, or a response longer than 5 seconds will be considered downtime. This will be the only measurement for SUSE compliance with the Service Commitment. All minutes qualifying under this section will be counted in the Actual Monthly Uptime Minutes.
AutoNDA by SimpleDocs

Related to Monthly Uptime Measurement

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Usage Measurement Usage measurement for calls shall begin when answer supervision or equivalent Signaling System 7 (SS7) message is received from the terminating office and shall end at the time of call disconnect by the calling or called subscriber, whichever occurs first.

  • Temperature Measurement Temperature will be measured by the nearest automatic Melbourne Bureau of Meteorology Monitoring Station for example (but not limited to): Melbourne, Moorabbin, Dunns Hill, Melbourne Airport, Frankston, and Point Xxxxxx. At the commencement of each project, the onsite management and employee representatives shall agree which is to be the applicable automatic weather monitoring station.

  • Performance Measurement The Uniform Guidance requires completion of OMB-approved standard information collection forms (the PPR). The form focuses on outcomes, as related to the Federal Award Performance Goals that awarding Federal agencies are required to detail in the Awards.

  • Measurement Should the State terminate this contract as herein provided, no fees other than fees due and payable at the time of termination shall thereafter be paid to the Engineer. In determining the value of the work performed by the Engineer prior to termination, the State shall be the sole judge. Compensation for work at termination will be based on a percentage of the work completed at that time. Should the State terminate this contract under paragraph (4) or (5) above, the Engineer shall not incur costs during the thirty-day notice period in excess of the amount incurred during the preceding thirty days.

  • Performance Measure Grantee will adhere to the performance measures requirements documented in

  • Measurement method An isolation resistance test instrument is connected between the live parts and the electrical chassis. The isolation resistance is subsequently measured by applying a DC voltage at least half of the working voltage of the high voltage bus. If the system has several voltage ranges (e.g. because of boost converter) in conductively connected circuit and some of the components cannot withstand the working voltage of the entire circuit, the isolation resistance between those components and the electrical chassis can be measured separately by applying at least half of their own working voltage with those components disconnected.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.

  • Measuring EPP parameters Every 5 minutes, EPP probes will select one “IP address” of the EPP servers of the TLD being monitored and make an “EPP test”; every time they should alternate between the 3 different types of commands and between the commands inside each category. If an “EPP test” result is undefined/unanswered, the EPP service will be considered as unavailable from that probe until it is time to make a new test.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!