Azure Monitor and CrateDB Integration

Input and output integration overview

Gather metrics from Azure resources using the Azure Monitor API.

The CrateDB plugin facilitates the writing of metrics to a CrateDB database, leveraging its PostgreSQL-compatible protocol to ensure a seamless experience for users.

Integration details

Azure Monitor

The Azure Monitor Telegraf plugin is specifically designed for gathering metrics from various Azure resources using the Azure Monitor API. Users must provide specific credentials such as client_id, client_secret, tenant_id, and subscription_id to authenticate and gain access to their Azure resources. Additionally, the plugin supports functionality to collect metrics from both individual resources and resource groups or subscriptions, allowing for flexible and scalable metric collection tailored to user needs. This plugin is ideal for organizations leveraging Azure cloud infrastructure, providing crucial insights into resource performance and utilization over time, facilitating proactive management and optimization of cloud resources.

CrateDB

This plugin writes to CrateDB via its PostgreSQL protocol, allowing for metrics to be efficiently stored in a scalable database. CrateDB is designed for high-speed analytics, supporting time-series data and complicated queries, making it ideal for applications that require fast ingestion and analysis of large datasets. By utilizing the PostgreSQL protocol, the CrateDB output plugin ensures compatibility with existing PostgreSQL client libraries and tools, enabling a smooth integration for users who are already familiar with PostgreSQL’s ecosystem. The plugin provides options such as automatic table creation, connection parameters, and query timeouts, offering flexibility in how metrics are handled and stored within the database.

Configuration

Azure Monitor

# Gather Azure resources metrics from Azure Monitor API
[[inputs.azure_monitor]]
  # can be found under Overview->Essentials in the Azure portal for your application/service
  subscription_id = "<>"
  # can be obtained by registering an application under Azure Active Directory
  client_id = "<>"
  # can be obtained by registering an application under Azure Active Directory.
  # If not specified Default Azure Credentials chain will be attempted:
  # - Environment credentials (AZURE_*)
  # - Workload Identity in Kubernetes cluster
  # - Managed Identity
  # - Azure CLI auth
  # - Developer Azure CLI auth
  client_secret = "<>"
  # can be found under Azure Active Directory->Properties
  tenant_id = "<>"
  # Define the optional Azure cloud option e.g. AzureChina, AzureGovernment or AzurePublic. The default is AzurePublic.
  # cloud_option = "AzurePublic"

  # resource target #1 to collect metrics from
  [[inputs.azure_monitor.resource_target]]
    # can be found under Overview->Essentials->JSON View in the Azure portal for your application/service
    # must start with 'resourceGroups/...' ('/subscriptions/xxxxxxxx-xxxx-xxxx-xxx-xxxxxxxxxxxx'
    # must be removed from the beginning of Resource ID property value)
    resource_id = "<>"
    # the metric names to collect
    # leave the array empty to use all metrics available to this resource
    metrics = [ "<>", "<>" ]
    # metrics aggregation type value to collect
    # can be 'Total', 'Count', 'Average', 'Minimum', 'Maximum'
    # leave the array empty to collect all aggregation types values for each metric
    aggregations = [ "<>", "<>" ]

  # resource target #2 to collect metrics from
  [[inputs.azure_monitor.resource_target]]
    resource_id = "<>"
    metrics = [ "<>", "<>" ]
    aggregations = [ "<>", "<>" ]

  # resource group target #1 to collect metrics from resources under it with resource type
  [[inputs.azure_monitor.resource_group_target]]
    # the resource group name
    resource_group = "<>"

    # defines the resources to collect metrics from
    [[inputs.azure_monitor.resource_group_target.resource]]
      # the resource type
      resource_type = "<>"
      metrics = [ "<>", "<>" ]
      aggregations = [ "<>", "<>" ]

    # defines the resources to collect metrics from
    [[inputs.azure_monitor.resource_group_target.resource]]
      resource_type = "<>"
      metrics = [ "<>", "<>" ]
      aggregations = [ "<>", "<>" ]

  # resource group target #2 to collect metrics from resources under it with resource type
  [[inputs.azure_monitor.resource_group_target]]
    resource_group = "<>"

    [[inputs.azure_monitor.resource_group_target.resource]]
      resource_type = "<>"
      metrics = [ "<>", "<>" ]
      aggregations = [ "<>", "<>" ]

  # subscription target #1 to collect metrics from resources under it with resource type
  [[inputs.azure_monitor.subscription_target]]
    resource_type = "<>"
    metrics = [ "<>", "<>" ]
    aggregations = [ "<>", "<>" ]

  # subscription target #2 to collect metrics from resources under it with resource type
  [[inputs.azure_monitor.subscription_target]]
    resource_type = "<>"
    metrics = [ "<>", "<>" ]
    aggregations = [ "<>", "<>" ]
</code></pre>

CrateDB

[[outputs.cratedb]]
  ## Connection parameters for accessing the database see
  ##   https://pkg.go.dev/github.com/jackc/pgx/v4#ParseConfig
  ## for available options
  url = "postgres://user:password@localhost/schema?sslmode=disable"

  ## Timeout for all CrateDB queries.
  # timeout = "5s"

  ## Name of the table to store metrics in.
  # table = "metrics"

  ## If true, and the metrics table does not exist, create it automatically.
  # table_create = false

  ## The character(s) to replace any '.' in an object key with
  # key_separator = "_"

Input and output integration examples

Azure Monitor

1. Dynamic Resource Monitoring: Use the Azure Monitor plugin to dynamically gather metrics from Azure resources based on specific criteria like tags or resource types. Organizations can automate the process of loading and unloading resource metrics, enabling better performance tracking and optimization based on resource utilization patterns.

2. Multi-Cloud Monitoring Integration: Integrate metrics collected from Azure Monitor with other cloud providers using a centralized monitoring solution. This allows organizations to view and analyze performance data across multiple cloud deployments, providing a holistic overview of resource performance and costs, and streamlining operations.

3. Anomaly Detection and Alerting: Leverage the metrics gathered via the Azure Monitor plugin in conjunction with machine learning algorithms to detect anomalies in resource utilization. By establishing baseline performance metrics and automatically alerting on deviations, organizations can mitigate risks and address performance issues before they escalate.

4. Historical Performance Analysis: Use the collected Azure metrics to conduct historical analysis by feeding the data into a data warehousing solution. This enables organizations to track trends over time, allowing for detailed reporting and decision-making based on historical performance data.

CrateDB

1. Real-Time Analytics for IoT Devices: Collect and store metrics from thousands of IoT devices. By setting up a dynamic metrics table for each device, users can perform real-time analytics on the collected data, enabling quick insights into device performance, patterns, and potential failures. This setup benefits from CrateDB’s ability to handle high-throughput data ingestion while providing the necessary analytics capabilities to derive actionable insights.

2. Website Performance Monitoring: Track key performance metrics from web applications, such as request latency and user activity. By storing metrics in CrateDB, teams can leverage the power of SQL-like queries to analyze traffic patterns, user engagement, and server performance over time, leading to optimized application performance and enhanced user experiences.

3. Financial Transaction Analysis: Manage large volumes of financial transaction data for real-time fraud detection and analysis. With CrateDB’s scalable infrastructure, users can store, query, and analyze transaction metrics efficiently, allowing for the detection of anomalies and illicit activities based on transaction patterns and trends.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.