Skip to main content

Data Integration

Overview

Data Integration is the entry module for the platform to connect to external data sources, supporting data retrieval from multiple data sources for metric creation and analysis. Data Integration includes the following two core functions:

  • Data Access: The platform provides more than ten data access templates, including:
    • Monitoring Platforms: Zabbix, Prometheus, Grafana
    • UniAgent: for Kubernetes, for Host, Collector, Mobile APP, Web, Mini Program
    • External Data: Database
  • Data Source: Displays created data access instances for managing and configuring specific data source connections.

Use Cases

When you need to create custom metrics, you can obtain data from monitoring tools, Agents, collectors, and external data to create metrics. Created metrics can be used to set alerts and display statistical data on dashboards.

Configuration Guide

  1. In Integration, create a specific data integration instance based on data access templates provided by the platform.
  2. In the Lite App Metric System > Generate, complete custom metric creation.

Prerequisites

You need to install a Collector that integrates with external data first.

For details, see Integrating External Data Source Data to install Collector for MySQL data collection.

Data Access

For different data access templates, fill in connection configuration parameters such as connection address, authentication, etc., to complete data source creation.

Using external data Database as an example:

StepItemDescription
1 Select CollectorCollectorSelect a collector that can connect to MySQL.
2 Data Source InformationData Source NameName of the specific database data source.
Data Source TypeMySQL
Data Source StatusEnable or disable. Default is enabled.
3 Connect to DatabaseHostIP address of the host where MySQL is located
PortPort of MySQL
Database NameDatabase name
UsernameUsername for connecting to MySQL database
PasswordPassword for connecting to MySQL database
Timeout (seconds)Maximum time to continue attempting connection after initial MySQL connection failure. No further connection attempts after exceeding this value.
4 Configuration CompleteNoneNone

Data Source Usage

After establishing a data source, metric data is typically obtained from the data through queries, statistics, and other statements.

Generating Metrics

Overview

Currently, the platform has two types of metric sources: one is metrics collected by system default Agents, and the other is metrics obtained through the data access function under Integration by connecting to external monitoring tools, platform internal business data, and data stored in third-party databases.

Configuration Guide
  1. Select the metric data source: Guanyun or MySQL.
  2. When selecting Guanyun, there are four types of model data (METRIC, SPAN, RUM, and LOG) that store business and performance data. Define metric attributes through model selection.
  3. When selecting MySQL, obtain metric data by configuring SQL query statements.
  4. After saving the configuration, the platform automatically distributes this configuration to the Collector in the configuration.
  5. The Collector completes metric collection work according to configuration parameters.
Creating Metrics from Guanyun Models

StepItemDescription
1 Select Data SourceGuanyunSelect the data source for creating metrics
2 ModelSelect ModelMETRIC: Create derived metrics or composite metrics from system metrics.
+ Metric, metrics that exist in the current system
+ Filter, metric attribute filtering
+ Metric Expression, when multiple metrics appear, generate new metrics through addition, subtraction, multiplication, and division
+ Metric Dimension, used to filter metric data
SPAN: Create metrics from SPAN model data in Traces.
+ Business System, existing business systems
+ Application, select corresponding application list under the business system
+ Data Item, data items configured under this business system
+ WHERE, data items configured under this business system
+ GROUP BY, data items configured under this business system
RUM: Obtain metric data from RUM protocol data.
+ VISUALIZE, select data attributes in the model as metrics
+ WHERE, data items configured under this business system
+ GROUP BY, data items configured under this business system
LOG: Obtain metric data from LOG protocol data.
3 Add MetricMetric KeyUnique identifier of the metric, usually named in English
Metric NameChinese meaning of the metric
Metric CategoryResource level classification of entities to which the metric belongs
Measurement StandardDefault neutral, used to determine whether a larger or smaller metric value is better
UnitUnit of the metric, displayed in user charts
Metric LevelImportance level of the metric
Metric Upper BoundMaximum value of the metric, exceeding which is abnormal
Metric Lower BoundMinimum value of the metric, default 0
Metric DescriptionMore explanatory information about this metric
4 Associate EntityTagsSystem default assignment
5 Configuration CompleteNoneNone
Creating Metrics from MySQL Data Source

StepItemDescription
1 Select Data SourceMySQLSelect a specific data source instance under data source type MySQL. After selection, the system displays basic information of this data source.
2 SQL QueryQuery StatementQuery statement that must start with Select
Data Query Time IntervalHow often to connect to the database to query SQL statements
3 Add MetricMetric KeyUnique identifier of the metric, usually named in English
Metric NameChinese meaning of the metric
Metric CategoryResource level classification of entities to which the metric belongs
Measurement StandardDefault neutral, used to determine whether a larger or smaller metric value is better
UnitUnit of the metric, displayed in user charts
Metric LevelImportance level of the metric
Metric Upper BoundMaximum value of the metric, exceeding which is abnormal
Metric Lower BoundMinimum value of the metric, default 0
Metric DescriptionMore explanatory information about this metric
4 Associate EntityTagsManually select associated business systems/applications.
5 Configuration CompleteNoneNone