2023.05

2023.05

  • Imply
  • Ingest
  • Query
  • Visualize
  • Administer
  • Deploy

›Clarity

Overview

  • About Imply administration

Manager

  • Using Imply Manager
  • Managing Imply clusters
  • Imply Manager security
  • Extensions

Users

  • Imply Manager users
  • Druid API access
  • Authentication and Authorization

    • Get started with Imply Hybrid Auth
    • Authentication
    • Local users
    • User roles
    • User groups
    • User sessions
    • Brute force attack detection
    • Identity provider integration
    • Okta OIDC integration
    • Okta SAML integration
    • LDAP integration
    • OAuth client authentication

Clarity

  • Monitoring
  • Set up SaaS Clarity
  • Cloudwatch monitoring
  • Metrics

Druid administration

  • Configuration reference
  • Logging
  • API reference
  • Druid design

    • Design
    • Segments
    • Processes and servers
    • Deep storage
    • Metadata storage
    • ZooKeeper

    Data management

    • Overview
    • Data updates
    • Data deletion
    • Schema changes
    • Compaction
    • Automatic compaction

    Security

    • Security overview
    • User authentication and authorization
    • LDAP auth
    • Dynamic Config Providers
    • Password providers
    • Authentication and Authorization
    • TLS support
    • Row and column level security

    Performance tuning

    • Basic cluster tuning
    • Segment size optimization
    • Mixed workloads
    • HTTP compression
    • Automated metadata cleanup

    View Manager

    • View Manager
    • View Manager API
    • Create a view
    • List views
    • Delete a view
    • Inspect view load status
  • Rolling updates
  • Using rules to drop and retain data
  • Alerts
  • Java runtime
  • Working with different versions of Apache Hadoop
  • Misc

    • dump-segment tool
    • reset-cluster tool
    • pull-deps tool
    • Deep storage migration
    • Export Metadata Tool
    • Metadata Migration

Cloudwatch monitoring

Amazon CloudWatch RDS monitoring can help you identify and avoid capacity or other issues with the metadata store for the cluster. With the Amazon CloudWatch integration, enabling metadata store monitoring for your cluster allows Imply support to track the health of your clusters and get notifications of potential issues. Specifically, alerts are triggered for these conditions:

  • CPU usage > 80% of capacity
  • Memory usage > 80% of capacity
  • Storage usage > 80% of capacity
  • Connections > 80% of max_connections

Note that using Amazon CloudWatch with Imply may entail additional costs, which are not included in the Imply subscription. See CloudWatch pricing for details.

Enabling metadata monitoring

Metadata monitoring is enabled by default for new clusters created after the availability of Imply version 3.4 (July, 2020).

For clusters that existed prior to that time, metadata store monitoring is disabled by default to avoid the possibility of interfering with existing settings or validated configurations.

You can enable metadata store monitoring as follows.

  1. As the Imply role in the AWS account needs permission to interact with Amazon CloudWatch, in the IAM settings, create a policy for Imply that enables the following permissions for the CloudWatch service:
  • Delete alarms (cloudwatch:DeleteAlarms): Required to delete an alarm.
  • DescribeAlarms (cloudwatch:DescribeAlarms): Required to retrieve alarm information by name.
  • PutMetricAlarm (cloudwatch:PutMetricAlarm): Required to create or update an alarm.
  1. Enable metadata store monitoring as follows:
    1. Navigate to the Cluster Page > Setup > Advanced Config.
    2. In the Metadata Storage section, set the metadata store monitoring value to Enabled.
    3. Click Apply changes.
Last updated on 11/3/2022
← Set up SaaS ClarityMetrics →
  • Enabling metadata monitoring
2023.05
Key links
Try ImplyApache Druid siteImply GitHub
Get help
Stack OverflowSupportContact us
Learn more
Apache Druid forumsBlog
Copyright © 2023 Imply Data, Inc