Skip to content

Latest commit

 

History

History
173 lines (147 loc) · 5.73 KB

elasticsearch.md

File metadata and controls

173 lines (147 loc) · 5.73 KB
Raw
description
This article explains how to configure an Elasticsearch repository

Elasticsearch

Overview

The ElasticSearch (ES) connector is based on the HTTP API exposed by ES instances.

{% hint style="info" %} Deprecated support for the native ES client

Gravitee no longer supports the native ES client. Previous connectors provided by Gravitee are no longer supported. {% endhint %}

Supported databases

Database Version tested
ElasticSearch 7.17.x / 8.8.x
OpenSearch 1.x / 2.x

Configuration

APIM API configuration

The ElasticSearch client does not support URL schemes in the format http://USERNAME:[email protected]. You must provide the username and password using the analytics.elasticsearch.security.username and analytics.elasticsearch.security.password properties.

analytics:
  type: elasticsearch
  elasticsearch:
    endpoints:
      - http://localhost:9200
#    index: gravitee
#    index_mode: daily    # "daily" indexes, suffixed with date. Or "ilm" managed indexes, without date
#    security:
#       username:
#       password:
#    ssl:                        # for https es connection
#      keystore:
#        type: jks               # required. also valid values are "pem", "pfx"
#        path: path/to/jks         # only for only for jks / pkcs12
#        password: <keystore pass> # only for only for jks / pkcs12
#        certs: 'path/to/cert'      # only for pems
#        keys: 'path/to/key'        # only for pems

API Gateway configuration

reporters:
  elasticsearch:
    enabled: true # Is the reporter enabled or not (default to true)
    endpoints:
      - http://${ds.elastic.host}:${ds.elastic.port}
#    index: gravitee
#    index_mode: daily    # "daily" indexes, suffixed with date. Or "ilm" managed indexes, without date
#    cluster: elasticsearch
#    bulk:
#      actions: 1000           # Number of requests action before flush
#      flush_interval: 5       # Flush interval in seconds
#      concurrent_requests: 5  # Concurrent requests
#    settings:
#      number_of_shards: 5
#      number_of_replicas: 1
#    pipeline:
#      plugins:
#        ingest: geoip
#    ssl:                        # for https es connection
#      keystore:
#        type: jks               # required. also valid values are "pem", "pfx"
#        path: path/to/jks         # only for only for jks / pkcs12
#        password: <keystore pass> # only for only for jks / pkcs12
#        certs: 'path/to/cert'      # only for pems
#        keys: 'path/to/key'        # only for pems

Index management with ES Curator

ES Curator is a tool for ES administration. To optimize the data footprint and ES performance, define a retention window and periodically merge shards into only one segment.

{% code overflow="wrap" %}

/usr/bin/curator --config /opt/curator/curator.yml /opt/curator/action-curator.yml

{% endcode %}

{% code title="curator.yml" %}

client:
  hosts:
    - node1
    - node2
  port: 9200

logging:
  loglevel: INFO
  logfile:
  logformat: default
  blacklist: ['elasticsearch', 'urllib3']

{% endcode %}

{% code title="action-curator.yml " %}

actions:
  1:
    action: forcemerge
    description: "Perform a forceMerge on selected indices to 'max_num_segments' per shard. Merge Days - 1 index for optimize disk space footprint on ElasticSearch TS"
    options:
      max_num_segments: 1
      continue_if_exception: True
      ignore_empty_list: True
    filters:
    - filtertype: pattern
      kind: prefix
      value: '^(gravitee-).*$'
      exclude: False
    - filtertype: age
      source: name
      direction: older
      unit: days
      unit_count: 1
      timestring: '%Y.%m.%d'
  2:
    action: delete_indices
    description: "Delete selected indices older than 15d days"
    options:
      continue_if_exception: True
      ignore_empty_list: True
    filters:
    - filtertype: pattern
      kind: prefix
      value: '^(gravitee-).*$'
      exclude: False
    - filtertype: age
      source: name
      direction: older
      unit: days
      unit_count: 15
      timestring: '%Y.%m.%d'

{% endcode %}

{% hint style="info" %} ES curator deployment hint

If you deploy ES Curator on every ES data node, set master_only: True in the curator configuration file. This ensures the curator is run only once on the elected current master. {% endhint %}

Index management with ES ILM

You can configure Index Lifecycle Management (ILM) policies to automatically manage indices according to your retention requirements. For example, you can use ILM to create a new index each day and archive the previous ones. See this documentation for more information.

By default, the index_mode configuration value is daily, where Gravitee suffixes index names with the date. To let ILM handle indexing, you can set index_mode to ILM. Gravitee will no longer add a suffix to index names. You also need to tell your APIM Gateway which ILM policies to use.

Here’s an example configuration for APIM Gateway:

  elasticsearch:
    enabled: true # Is the reporter enabled or not (default to true)
    endpoints:
      - http://${ds.elastic.host}:${ds.elastic.port}
    lifecycle:
      policies:
        health: hot_delete_health # ILM policy for the gravitee-health-* indexes
        monitor: hot_delete_monitor # ILM policy for the gravitee-monitor-* indexes
        request: hot_delete_request # ILM policy for the gravitee-request-* indexes
        log: hot_delete_log # ILM policy for the gravitee-log-* indexes
    index_mode: ilm         # "daily" indexes, suffixed with date. Or "ilm" managed indexes, without date