Overview

Monitoring Service is a cloud-based service that allows you to ingest, aggregate, and analyze data to enhance your understanding of your system's performance and behavior. The service collects data from various parts of your environment into a central system that is responsible for storage, aggregation, visualization, and initiating automated responses and alert when certain conditions are met.

Components of Monitoring Service

The architecture of the Monitoring Service includes the following four main components that can be used to aggregate metrics from various sources, analyze the gathered metrics, and create visualizations for monitoring and report generation.

• Data Collection: Data collection involves gathering metrics to track system performance and health. During this phase, metrics are collected by an agent running on each monitored resource. These metrics are then pushed to the Monitoring Service, ensuring that all relevant performance and behavior data from various parts of the environment are efficiently gathered.

• Data Aggregation & Processing: Once the data reaches the Monitoring Service, it undergoes aggregation and processing. This step prepares the data for storage by transforming and organizing it to optimize subsequent retrieval and analysis.

• Indexing & Storage: Indexing and storage in monitoring services ensure that collected data is organized and accessible for quick retrieval and analysis. Indexing involves creating searchable metadata for the data, enabling efficient queries. Storage involves saving the data in a scalable and durable manner, often using databases or specialized storage systems designed for high write and read performance.

• Visualization & Analysis: Visualization in monitoring services involves displaying collected and processed data in an intuitive and accessible format. Users can access their metrics for visualization, reporting, analysis, and alerting through a dedicated Grafana Instance. This provides comprehensive tools for interpreting the collected metrics, enabling informed decision-making and proactive system management.

Product Limitations

The following are the key limitations of the Monitoring Service:

Parameter	Description	Limit
max_global_series_per_user	The maximum number of time series a single user can manage.	150,000 series
max_metadata_length	Maximum length for metric metadata, including Metric Name, #HELP, and UNIT.	1024 characters
max_label_names_per_series	Maximum number of label names allowed per time series.	30 label names
max_label_value_length	Maximum length for any label value.	2048 characters
max_label_name_length	Maximum length for any label name.	1024 characters
ingestion_burst_size	Maximum number of samples that can be ingested in a single burst.	200,000 samples
ingestion_rate	Maximum number of samples that can be ingested per second.	10,000 samples/Sec