Watcher Utilization Data Sample Clauses

Watcher Utilization Data. As of version 9.2 onward of the Cloudshell Software, the CloudShell Software will include an additional service (''CloudShell Watcher'') collecting CloudShell utilization information including information regarding your CloudShell reservations (''Sandboxes'') such as max concurrent Sandboxes per day, total Sandboxes started per day, number of unique uses per day, number of public Blueprints, number of Blueprints with active Sandbox per day - this general aggregate information is kept in a secure and protected manner and is not related to any specific CloudShell user or person. This data being collected collects no personal information, no customer password information, personal information or information regarding any of your content and is being sent online to QualiSystems (''Watcher Utilization Data''). The Watcher Utilization Data is saved locally to the CloudShell server machine (''CloudShell Server''). For the purpose of collection of the Watcher Utilization Data the CloudShell Server will send, periodically, via internet connection, the Watcher Utilization Data to QualiSystems’s dedicated storage located on the Cloud , in a secured, anonymized and encrypted manner. You hereby confirm that you are aware that, and provide your full consent to have the Watcher Utilization Data on the CloudShell Server sent to QualiSystems as detailed above. QualiSystems shall be entitled to make use of such Watcher Utilization Data for and in order to enhance your usage of the Software including by offering optimization of your utilization of the Software as well as assistance in monitoring of the Software for possible malfunctions and the ongoing improvement of our products, and Your use abilities and subject to our current Privacy Policy. For the purpose of possible malfunctions detection, locally stored Watcher Utilization Data will also be collected by QualiSystems during Service or Support request relating to the Software. The Watcher Utilization Data will be collected by the CloudShell monitor (which is already inherent part of CloudShell). The CloudShell monitor should be executed on the CloudShell Sever and then the Watcher Utilization Data will be packed together with the logs (which are collected by the monitor).
AutoNDA by SimpleDocs

Related to Watcher Utilization Data

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • Utilization Scale STATE shall scale logs or portions of logs that are broken, wasted, or not removed by PURCHASER due to: (1) improper felling or bucking of the logs; (2) failure to remove the logs prior to deterioration; and (3) logs remaining on the timber sale area after completion of logging, provided the logs were merchantable prior to breakage or wastage. Material used to meet down material requirements in the section titled, "Reserved Timber," shall not be considered for utilization scale. PURCHASER shall pay for the logs at the contract price designated in Section 44. STATE shall notify PURCHASER of the volume of logs so scaled. Payment shall be considered due on such volume as if the logs were removed on the date of said notification. In the event PURCHASER disagrees with the findings made by STATE under this section, PURCHASER may furnish scaling by a third-party scaling organization acceptable to STATE. Costs and expenses of such third party shall be paid for by PURCHASER, and the findings of the third party shall be final.

  • System Availability System Availability percentage is calculated as follows:  Total MinutesintheMonth −Downtime   System Availability%age =  Total MinutesintheMonth *100    System Availability SLA (“SLA”) 99.5% System Availability percentage during each Month for productive versions Credit 2% of Monthly Subscription Fees for each 1% below SLA, not to exceed 100% of Monthly Subscription Fees Excluded Downtime Total Minutes in the Month attributable to: (i) a Scheduled Downtime for which a Regular Maintenance Window is described in Section 4 below, or (ii) any other Scheduled Downtime according to Section 4 for which the customer has been notified at least five (5) business days prior to such Scheduled Downtime or (iii) unavailability caused by factors outside of SAP’s reasonable control, such as unpredictable and unforeseeable events that could not have been avoided even if reasonable care had been exercised. Scheduled Downtime Scheduled Downtime for the applicable Cloud Services to which customer has subscribed is set forth in Section 4 below entitled “Maintenance Windows for Cloud Services”.

  • Utilization Utilization shall be defined as Trunks Required as a percentage of Trunks In Service.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • MWBE Utilization Plan A. In accordance with 5 NYCRR § 142.4, Bidders are required to submit a completed Utilization Plan on Form MWBE 100 with their bid.

  • DNS service availability Refers to the ability of the group of listed-­‐as-­‐authoritative name servers of a particular domain name (e.g., a TLD), to answer DNS queries from DNS probes. For the service to be considered available at a particular moment, at least, two of the delegated name servers registered in the DNS must have successful results from “DNS tests” to each of their public-­‐DNS registered “IP addresses” to which the name server resolves. If 51% or more of the DNS testing probes see the service as unavailable during a given time, the DNS service will be considered unavailable.

  • Uptime bookinglab shall ensure that the Booking Service will be available, excluding Downtime caused by Scheduled Maintenance, Emergency Maintenance or Force Majeure event, 99.5% of the time in any one calendar month (first day to last day) (the “Service Level”). The Service Level will not apply (and therefore no Service Credits will be applicable) to the extent that any Service Level Failure is caused by: (a) a Penetration Test conducted by Customer without the prior written approval of bookinglab; or (b) Customer’s failure to comply with specific instructions provided by bookinglab; or (c) a failure of the Customer to comply with any Customer responsibility or obligation detailed in a Statement of Work, Order Form or the Master Subscription Agreement; or (d) Customer’s failure to adhere to JRNI’s or bookinglab’s best practice guidelines for the use of the API.

  • Utilization Reports Both the Contractor and Subcontractor shall complete Quarterly Utilization Reports (or similar type documents containing the same information) and submit them to the Contracting Officer and to the Bureau within ten (10) business days at the end of each quarter. This information will be used to determine the actual dollar amount paid to Subcontractor and will also serve as a record of fulfillment of Contractor’s Small Diverse Business and Small Business Commitments. If there was no activity during the quarter, then the form must be completed by stating “No activity in this quarter.” A late fee of $100.00 per day may be assessed against the Contractor if its Utilization Report is not submitted in accordance with the schedule above.

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