Glossary
This article introduces the terminologies and basic concepts related to AutoMQ Cloud, to enhance your understanding and usage of AutoMQ Cloud.
In this article, references to AutoMQ product and service providers, AutoMQ service sides, and AutoMQ specifically denote "AutoMQ CO." based in Hangzhou.
Based on a top-down and detailed categorization principle, the main terminological and conceptual relationships are illustrated in the following diagram:
Terminology Details
Subscription Plan
A Subscription Plan is a service payment agreement chosen by the user in AutoMQ Cloud. It specifies the payment method, pricing, service duration, and resource quotas for the software services provided by AutoMQ Cloud.
Subscription Status
Subscription Status indicates the life cycle state of a Subscription Plan. It determines the current state of the plan, whether it is active or expired, among other details. Subscription status generally consists of two enumerated states: active and expired.
Environment
An environment comprises essential configuration information that is shared across various products within AutoJ at the operational level. It includes elements like infrastructure type, region, and network configurations, and is the realm in which all physical resources of AutoMQ Cloud are managed and deployed.
Environment Status
The environment status indicates the current deployment and operational condition of the environment, revealing whether it is under maintenance, experiencing disruptions, or approaching service expiration. Common states include 'Being Created', 'In Service', 'Service Disruption', and 'Undergoing Changes'.
Instance
In AutoMQ Cloud, an instance functions similarly to a cluster in open-source Apache Kafka®. It encompasses metadata that outlines the lifecycle, constraints, and specific configurations of a cluster. Additionally, each instance is equipped with various status indicators that monitor the service's current operational state.
Member
Within AutoMQ Cloud, a member is an operational account responsible for managing product resources. AutoMQ Cloud distinguishes between three member roles: Admin, Operator, and Viewer, each with unique operational privileges. For additional information, refer to Overview▸.
Integration
Integration pertains to the configurations set at the environmental level in AutoMQ Cloud, aimed at enhancing data interchange with other third-party SaaS systems. For example, users can establish a Prometheus integration and subsequently forward Metrics data from specific Kafka instances to this tailor-made Prometheus setup, thereby facilitating tailored Metrics visualization and utilization. For additional information on integration, please see Manage Integrations▸.