Showing: 1-23 of 23
Affected sensors % threshold is the threshold when an alarm will be raised if the alarm is attached to more then one sensor. For example, if you have 10 sensors covered by the alarm and the 'Affected sensors % threshold' is set to 30%, the alarm will fire when 3 or more different sensors have breached the alarm threshold.
An alarm is an entity with the CloudReady system that can be used to detect abnormal conditions. Typically, CloudReady automatically configures alarms as sensors are deployed.
An Alarm Recipient Group is a list of (currently) email addresses and phone numbers to send to when an Alarm condition is detected. Alarm Recipient Group's are attached to an Organization. Each alarm can have one Alarm Recipient Group.
This value is the duration, in milliseconds, of how long it takes to connect and authorize with email provider.
A Deployment Key is a unique perishable token that has an associated public/private key pair associated with it on secure.exoprise.com. Deployment keys are used to uniquely identify Secure Service executables at installation time. Deployment keys enable customers to package and automate Secure Service installations.
DOM stands for Document Object Model. CloudReady frequently measures how long it takes the browser to load the DOM for a web page. This is typically when a webpage will start to become interactive for a user. See more here.
Draggable layouts are new tabs within the CloudReady customizable dashboard that can be fully configured with various different widgets. Each widget can be positioned and resized within the tab.
List layouts are new tabs within the CloudReady cutomizable dashboard and are composed of lists of widgets for each sensor that a user has access to. List layouts can be easily sorted and filtered but the widgets are in fixed positions.
This is the Exoprise custom network client that you use to deploy and manage Private Sites, train and reconfigure CloudReady Sensors. The Exoprise Management Client looks like a browser but is designed to only be used by Exoprise web sites.
MTA stands for Message Transfer Agent. See more here: en.wikipedia.org/wiki/Message_transfer_agent
Organizations represent an account within CloudReady. Organizations own users, sites and sensors for monitoring cloud services. Payment and billing records are tied to an Organization.
A sensor deployed to a Private Site
A Private Site is an instance of our Secure Service that you run where you want to measure performance from - typically behind the firewall where end-users use your applications. You can deploy a Private Site anywhere you want; on a desktop, server, spare VM or even in the cloud itself. A Private Site maintains constant communication with the CloudReady servers and runs sensors that are assigned to the Private Site.
A sensor deployed to a Public Site
A Public Site is maintained by Exoprise in various public clouds that you can deploy your own CloudReady sensors to measure the external internet facing performance of your web sites and to monitor the performance of cloud services for your mobile or remote users. Public Site sensors can be good for comparing against Private Site sensors.
Software as a service (or SaaS) is a way of delivering applications over the Internet—as a service. Instead of installing and maintaining software, you simply access it via the Internet, freeing yourself from complex software and hardware management.
This is our service executable that is deployed to run Sensors and other hybrid cloud-automation services. An instance of the Exoprise Secure Service is also referred to as a Site or Private Site.
A sensor monitors the performance of specific applications and services. You configure and deploy sensors where you want to measure performance from. You can deploy sensors to:
A Site is an instance of our Secure Service that runs sensors. You install Private Sites at various locations within your organization and then assign sensors to your sites to monitor web applications and services. Sites (public or private) run sensors.
This is the account that owns the CloudReady Site within the CloudReady Servers. This account is different from the Windows Service Account that owns the the process or Win32 Service on the deployed computer. Currently, only the Site Account can deploy sensors to the site.
Teams give organizations the ability to create groups of members and control access to sites and sensors within a company. Team members can be granted read, write, or admin permissions to specific sites and sensors.
Time to First Byte. This is a critical performance measurement and often indicative of how slow a server and network are for a user. TTFB or Time-to-First-Byte is the time it takes to receive the first byte of data from the server after a request is sent.
CloudReady Private Sites can be installed to run as Local System or as a local or domain-based User Account. For larger deployments that want central control you can choose to use a domain-based account.