Amazon Elasticsearch Service is a fully managed service that is easy to deploy, easy to secure, and cost effective at scale.
- Support for the tools that build, monitor, and troubleshoot your applications at the scale that you need.
- Support for open source Elasticsearch APIs, managed Kibana, integration with Logstash and other AWS services, and built-in alerting and SQL querying.
- Pay for only for what is used with no upfront costs or usage requirements. For example, you can get the ELK stack that you need, without the operational overhead.
Use the AWS public cloud integration to discover and collect metrics against the AWS service.
To set up the AWS integration and discover the AWS service, go to AWS Integration Discovery Profile and select
Elastic Search Service.
CloudTrail event support
- Configurable in OpsRamp AWS Integration Discovery Profile.
CloudWatch alarm support
- Not Supported
|OpsRamp Metric||Metric Display Name||Unit||Aggregation Type|
Number of nodes in the Amazon ES cluster.
Total number of searchable documents across all indices in the cluster.
Total number of deleted documents across all indices in the cluster.
Maximum percentage of CPU resources used for data nodes in the cluster.
Free space, in megabytes, for all data nodes in the cluster.
Total used space, in megabytes, for a cluster.
Indicates whether the cluster is accepting or blocking incoming write requests.
Maximum percentage of the Java heap used for all data nodes in the cluster.
Number of failed automated snapshots for the cluster.
Remaining CPU credits available for data nodes in the cluster.
Health check for Kibana.
Maximum percentage of CPU resources used by the dedicated master nodes.
Maximum percentage of the Java heap used for all dedicated master nodes in the cluster.
Remaining CPU credits available for dedicated master nodes in the cluster.
Health check for MasterNotDiscovered exceptions. Value of 1 indicates normal behavior.
Indicates that all index shards are allocated to nodes in the cluster.
Indicates that the primary shards for all indices are allocated to nodes in a cluster, but the replica shards for at least one index are not.
Indicates that the primary and replica shards of at least one index are not allocated to nodes in a cluster.
Number of requests to the domain that resulted in the given HTTP response code 2xx.
Number of requests to the domain that resulted in the given HTTP response code 3xx.
Number of requests to the domain that resulted in the given HTTP response code 4xx.
Number of requests to the domain that resulted in the given HTTP response code 5xx.
Value of 1 means that the alerting index is red or one or more nodes is not on schedule. Value of 0 indicates normal behavior.
Value of 1 means the .opendistro-alerting-config index exists. Value of 0 means it does not. Until you use the alerting feature for the first time, this value remains 0.
Health of the index. Value of 1 means green. Value of 0 means that the index doesnt exist or isnt green.
Health of the index. Value of 1 means red. Value of 0 means that the index does notexist or is not red.
Health of the index. Value of 1 means yellow. Value of 0 means that the index does not exist or is not yellow.
Value of 1 means some jobs are not running on schedule. Value of 0 means that all alerting jobs are running on schedule (or that no alerting jobs exist). Check the Amazon ES console or make a _nodes/stats request to see if any nodes show high resource usage.
Value of 1 means that all alerting jobs are running on schedule (or that no alerting jobs exist). Value of 0 means some jobs are not running on schedule.
Value of 1 indicates that, in response to certain requests, the SQL plugin is returning 5xx response codes or passing invalid query DSL to Elasticsearch. Other requests should continue to succeed. Value of 0 indicates no recent failures. If a sustained value of 1 is displayed, troubleshoot the requests that clients are making to the plugin.
Number of requests to the Open Distro SQL API.
Value of 1 means that the opendistro.scheduled_jobs.enabled cluster setting is true. Value of 0 means it is false and scheduled jobs are disabled.
Number of requests to the Open Distro SQL API API that failed due to a server problem or feature limitation. For example, a request might return HTTP status code 503 due to a VerificationException.
Number of requests to the Open Distro SQL API that failed due to a client issue. For example, a request might return HTTP status code 400 due to an IndexNotFoundException.