# Glossary of terms used in Acure
Action - the Acure system object that launches Automation Scripts or Actions Alerts based on the conditions of the Rule.
Agent - program running on Windows/Linux designed to perform Data Stream Tasks to collect information.
Autotests (ex. Testforge) - project management module for functional testing of information systems.
Availability - the ability of a service or service component to perform a required function at a specified moment or over a specified period of time.
CMDB - сonfiguration management database. A data storage used to record CI attributes and relationships between CIs throughout their lifecycle.
Collector - module for collecting and analyzing primary data.
Configuration Item (CI) - a system object - any element of an infrastructure or a service that needs to be managed to ensure the successful delivery of services. An example of a top-level CI is an information system that can have many subordinate (child) CIs, such as: operating system, application software, and hardware components. It is an object of the Service model (SM) and is characterized by "type of CI", "attributes", "state in the life cycle", "owner", "relationships (connections) with other CIs" and "health".
Coordinator - the object of the Acure system for distributing and controlling the execution of tasks on the Agents connected to it.
Custom report - Availability Report (SLA) with the possibility of obtaining it without time limits for generation.
Data stream (integration) - a system object that describes the data source connected to Acure.
ETL (Extract, Transform, Load) - the process of extraction, transformation and loading data collected from various sources.
Exercise - a set of instructions for execution by the Agent in the Yaml language.
Functional testing - verification that the Information systems functional requirements are compliant with their real characteristics.
Handler - Lua script for preprocessing (parsing) events in the Data Stream.
Incident - an unplanned event that has or may result in the interruption of a service or a reduction in its quality, even if it has not yet affected the service to the customer.
Integral event - an event generated by Acure signals based on the primary event.
Newsletter - configuration of the notification method and lists of notification recipients (Users, Roles, Workgroups).
Notification method - extension of the system functionality within the Userspace available for the list of Workgroups. The operation of the Notification Method is determined by the executable Lua script. Used to set up integrations with various messengers and Service Desk.
Owner - working group that owns the system object and has full rights to it.
Parametric filter - a filter that defines a dynamic set of CIs based on conditions (links, status, owner).
Prefilter - conditions under which primary events will be processed by the Synthetic Trigger.
Primary event - an event received through the collector and written to the ClickHouse database.
Public APIs - a set of methods, properties, events, and URLs that allow interaction between Acure, which provides the API, and other program components.
Report multi-template - a group of availability report templates.
Report Template - an Acure system object with preconfigured Availability report calculation options.
Report - the result of calculating the state of the information system, in which you can view the availability status of one device or the entire information system for a certain period of time.
Role - specifies the set of Access Rights granted to the user. Access rights are assigned to members using the Default Role or Custom Role. The role is assigned to the User the moment they are added to the Workgroup.
Rule - a set of conditions for automatically handling integral events and next executing Action.
Script (scenario) - an Acure system object that defines a sequence of actions described using the Lua scripting programming language to perform certain tasks automatically.
Service mode - a defined period of time during which planned outages and planned changes are possible for the services and systems provided. Maintenance periods are designed to allow customers to prepare for potential outages or changes.
Service model (SM) - a logical model of a service that describes the composition and relationships of a set of Configuration Items that together provide a service at an agreed level.
Service Model Graph - an abstract representation of a set of Configuration Items and relationships between them in a topology graph.
Service Model Map - an object of Acure representing a dynamic set of Configuration Items built according to the conditions of the Parametric Filter and storing the coordinates of the vertices of objects on the Service Model Graph.
Signal - “short-living" dynamic object driven by script in a low-code engine, similar to a task in a regular task tracker. The signal is opened by a certain alert (or a set of alerts), further in the process other alerts (confirming ones) can be attached to it and is closed by an alert or a scheduler event.
SLA - the Service Level Agreement defines the agreement and formal obligations between the service provider and the customer.
Timeline - timeline for grouping information in chronological order. Represents the horizontal line on which issues are displayed in the timeline.
User group - a customizable list of Userspace members. Does not define user access rights within the system and user access rights to objects.
User rights - a set of rules regulating the conditions for accessing Acure objects .
User - a person who uses a system to solve the tasks of automating monitoring processes.
Userspace administrator - the Acure system user with permissions to configure Userspace
Userspace - this is a logical unit separated from the main space, in which a single set of rules operates. Each Userspace has its own domain and name.
VM - a virtual machine is a software or hardware environment that emulates the hardware of some platform.
Workgroup - a group of users assigned to specific monitoring projects in the Acure system