Monium object configuration

To logically separate telemetry data, Monium uses configuration objects: project, cluster, service, and shard.

• Project: Top-level logical entity. You can use projects to aggregate telemetry from associated applications and microservices and restrict data access for development teams. Some examples include an online store, billing system, or security services. The system automatically creates a project associated with a Yandex Cloud folder. You can also create custom projects to logically separate telemetry within a single folder.

• Cluster: Allows you to isolate an environment or independent service installations, e.g., production and test clusters, clusters in different regions.

• Service: Standalone client application generating telemetry data. This may be a microservice or its component, e.g., Nginx, Envoy, or Compute Cloud VM instance.

• Shard: Container for data of a specific service-cluster pair and data storage settings, e.g., TTL.

The project, cluster, and service objects define the data source, and the shard defines the storage rules.

Data model mappingData model mapping

Configuration objects map to the required telemetry attributes in the data model:

• project
• cluster
• service

These attributes are included in every query in the query language and help narrow down the search scope. The more precisely the project, cluster, and service are specified, the faster the query runs.

See alsoSee also

• Data model in Monium.Metrics
• Query language in Monium
• Query string in Monium