Unryo Glossary

Here is a quick overview of the different terms used:

Term	Description
Alert Rule	Rules are attached to a dashboard panel. A rule contains the evaluation criterias, the query condition, and the destination notification channel(s) - i.e. email, notification tools, chat tools, etc. -.
Collector	The Unryo Platform uses collectors to gather data. A collector is installed on a customer host machine, in the form of a docker container. It collects data in an agentless way data from multiple sources, and redirect the data flow to the Unryo database for persistence.
Dashboards	Set of chart panels, organized and arranged into one or more rows, to present data to users, using certain display preferences.
Docker	An open platform for distributed applications, which allows you to assemble multi-container portable apps. For more information about Docker, see the Docker website.
ML Pack	Unryo Machine Learning Packs (or Unryo ML Packs) are predefined integrations to monitor a particular technology. They dictate how to collect the data, and how to present it. They contain data collection templates, analytics rules, and predefined dashboards.
Namespace	Environment where the components belong. It is used to create a network of services, to implement multitenancy among the same owner of applications.
Notification	The message sent when an alert rule is triggered
Notification Channel	The destination of a notification (can be emailed, Slack, Pagerduty or other integrations). See the list here
Source	Unique application, host, container, device or instance that emits metrics and/or logs.
Time Series	A series of timestamped values of a specific measurement
Unryo Control UI	A cloud-native console for life-cycle management of deployed components. From it, admins get access to a visual wizard for easy deployment of components. Also, get access to a live topology map that shows from a single point all the deployed components with their interconnectivity status, as well as health metrics.
Unryo Component	A component has a type (Collector, Portal, etc.), a role, and relations.
Unryo Component Role	The role of a component is used to build the relationships and interconnections with other components. The protocol supports four roles: producer, supplier, receiver, consumer. The producer role states that the component will produce data, supplier role.
Unryo Connect	Central and global cloud registry service that ensures secure and automatic interconnectivity and provides administrators an effortless way to control every component and deploy new ones.
Unryo Enterprise	Unryo Enterprise is the hybrid multi-cloud offering of the Unryo Monitor platform, where you deploy the Unryo platform components on your own infrastructure (on-premise, your clouds). All components are driven by the Unryo Connect service to ensure security and auto-connectivity.
Unryo Monitor	Unryo Monitor is a modern monitoring platform for infrastructure, clouds, and applications. You can either use it as-a-service (Unryo SaaS) or deploy in your hybrid multi-cloud environment (Unryo Enterprise).
Unryo SaaS	Unryo SaaS is the fully managed, and cloud hosted offering of the Unryo Monitor platform.
Unryo Tokens	Tokens are unique identifier associated with your organization. For your protection, treat them as you would a password. Never share tokens with other users or application.
User	A User is a named account in Unryo. A user can belong to one or more Organizations, and can be assigned different levels of privileges through roles.
Producer	A producer produces data of in a particular format. A producer's role is to push this data to an endpoint of a particular role, typically of a receiver.
Supplier	A supplier makes data available to other components in a particular format. A supplier's role is to expose an endpoint of a particular role, typically used by a consumer.
Receiver	A receiver receives data in a particular format. A receiver's role is to export an endpoint of a particular role, typically used by a producer.
Consumer	A consumer fetches data in a particular format. A consumer's role is to fetch data from an endpoint of a particular role, typically from a supplier.