Elasticsearch Search Requests Analysis/Audit
> Documentation > Docs > INFINI Gateway > Tutorials > Elasticsearch Search Requests Analysis/Audit

Elasticsearch Search/Request Log Analysis/Audit #

INFINI Gateway can track and record all requests that pass through the gateway and analyze requests sent to Elasticsearch, to figure out request performance and service running status.

Gateway configuration modification #

After extracting the Extreme Gateway installation package, there will be a default configuration file called ‘gateway.yml’. With a simple modification, traffic analysis can be achieved. Typically, only this section needs to be modified. The configuration items after this will reference the defined content through variables.

  LOGGING_ES_ENDPOINT: http://localhost:9200
  LOGGING_ES_USER: elastic
  LOGGING_ES_PASS: password
  PROD_ES_ENDPOINT: http://localhost:9200
  PROD_ES_USER: elastic
  PROD_ES_PASS: password

The above configuration defines two ES clusters and the gateway’s listener information.

  • LOGGING_ES_ENDPOINT : Define the access information of the log cluster, and all request logs will be written to this cluster.
  • PROD_ES_ENDPOINT : Define the access information of the production cluster, the gateway will proxy this cluster.
  • *_ES_USER and *_ES_PASS : Define the authentication information of the cluster.
  • API_BINDING : Define the address and port that the gateway API service listens on.
  • GW_BINDING Define the address and port that the gateway proxy service listens on.

In the test environment, the log cluster and production cluster can be the same.
Please make sure that requests to access the ES cluster are sent to the address and port that the gateway proxy service is listening on.

The gateway comes with a cache function. If you need to enable this feature, please modify the default_flow configuration as follows:

  - name: default_flow
      - get_cache:
      - elasticsearch:
          elasticsearch: prod
          max_connection_per_node: 1000
      - set_cache:

INFINI Easysearch #

INFINI easysearch supports higher compression rates, which is more conducive to saving disk space.
If the log cluster is using INFINI easysearch, it is important to install the index-management plugin.
Please click here to view the plugin installation documentation

bin/easysearch-plugin install index-management

After installing the plugin, restart for it to take effect.

Configure the index template. #

If you are already using INFINI Console, you can skip configuring the index lifecycle and index template because they have already been automatically created.

Execute the following command on the log cluster to create an index template for the log index.

Please note that you may need to modify the above template settings before executing, for example, by adding the routing.allocation.require parameter to specify the node attribute where the index is created.

Configuring the Index Lifecycle #

Importing the Dashboard #

Download the latest dashboard INFINI-Gateway-7.9.2-2021-01-15.ndjson.zip for Kibana 7.9 and import it into Kibana of the dev cluster as follows:

Starting the Gateway #

Start the gateway.

➜ ./bin/gateway
   ___   _   _____  __  __    __  _
  / _ \ /_\ /__   \/__\/ / /\ \ \/_\ /\_/\
 / /_\///_\\  / /\/_\  \ \/  \/ //_\\\_ _/
/ /_\\/  _  \/ / //__   \  /\  /  _  \/ \
\____/\_/ \_/\/  \__/    \/  \/\_/ \_/\_/

[GATEWAY] A light-weight, powerful and high-performance elasticsearch gateway.
[GATEWAY] 1.0.0_SNAPSHOT, a17be4c, Wed Feb 3 00:12:02 2021 +0800, medcl, add extra retry for bulk_indexing
[02-03 13:51:35] [INF] [instance.go:24] workspace: data/gateway/nodes/0
[02-03 13:51:35] [INF] [api.go:255] api server listen at:
[02-03 13:51:35] [INF] [runner.go:59] pipeline: request_logging_index started with 1 instances
[02-03 13:51:35] [INF] [entry.go:267] entry [es_gateway] listen at:
[02-03 13:51:35] [INF] [app.go:297] gateway now started.

Modifying Application Configuration #

Replace the Elasticsearch address with the gateway address for applications directed to the Elasticsearch address (such as Beats, Logstash, and Kibana). Assume that the gateway IP address is Modify the Kibana configuration as follows:

# The Kibana server's name.  This is used for display purposes.
#server.name: "your-hostname"

# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: [""]
elasticsearch.customHeaders: { "app": "kibana" }

# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true

# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
#kibana.index: ".kibana"

# The default application to load.
#kibana.defaultAppId: "home"

Save the configuration and restart Kibana.

Checking the Results #

All requests that access Elasticsearch through the gateway can be monitored.