FME Server

Procedure

  1. Executing the statements from dev-console/ct-fme-*.txt in the Kibana Dev Console

  2. Importing Kibana Dashboards, Queries and Index Patterns from kibana/ct-fme/export.ndjson

  3. Setting up the logstash pipelines logstash/ct-fme-* (see below)

  4. Setting up the ingest pipelines from ingest/ct-monitor-fme.txt (see below)

It makes sense to create a separate user account in FME Server explicitly for the connection to service.monitor and to generate an FME token for these users.

Setting up the Logstash Pipelines

If all logstash pipeline folders of service.monitor are already present in Logstash, the three FME pipelines must be "activated" via the file pipelines.yml.

Configure pipeline

The FME pipelines must be configured by setting variables before they can be successfully commissioned.

Variable default explanation

FME_SERVER_BASE_URL

<empty>

URL of the host on which FME is running, incl. protocol, e.g.: https://fme.server.example/

FME_SERVER_TOKEN

<empty>

FME Server Token for authentication of the request at FME

FME_SERVER_LIMIT

1000

Number of jobs to be queried per request at FME Server

FME_SERVER_SCHEDULE

6h

Polling interval for FME Server jobs

ES_HOST

localhost

Specify the address of Elasticsearch, e.g. "127.0.0.1" or "https://elastic.server.example/extrapath"

ES_USER

<empty>

User name for authentication with Elasticsearch

ES_PASSWORD

<empty>

Password for authentication with Elasticsearch

Publish Elastic Ingest Pipeline

The contents of

  • ingest/ct-monitor-temporal.txt

  • ingest/ct-monitor-fme.txt

to be sent via the Kibana Dev Tools > Console.