Your connector has not connected to Search

Elastic Stack Elasticsearch
,
1

I am running mongo, elastic, kibana, and elastic-connectors in docker containers with docker-compose.

I setup the connector and config, and it even connects in docker logs.

[FMWK][21:01:02][INFO] Running connector service version 8.14.3.0
elastic-connectors-1  | [FMWK][21:01:02][INFO] Loading config from /config/config.yml
elastic-connectors-1  | [FMWK][21:01:02][INFO] Running preflight checks
elastic-connectors-1  | [FMWK][21:01:02][INFO] Waiting for Elasticsearch at https://es01:9200 (so far: 0 secs)
elastic-connectors-1  | [FMWK][21:01:02][INFO] Extraction service is not configured, skipping its preflight check.
elastic-connectors-1  | [FMWK][21:01:02][INFO] [job_scheduling_service] Job Scheduling Service started, listening to events from https://es01:9200
elastic-connectors-1  | [FMWK][21:01:02][INFO] [content_sync_job_execution_service] Content sync job execution service started, listening to events from https://es01:9200
elastic-connectors-1  | [FMWK][21:01:02][INFO] [access_control_sync_job_execution_service] Access control sync job execution service started, listening to events from https://es01:9200

However, in kibana UI no matter what I do all I see is:

image
image1043×350 20.2 KB

2

@Dedicated_Server what are the contents of the config.yml you're using when you run the connector service? Please redact all credentials before sharing.

My guess is that you haven't added

connectors:
  -
    connector_id: "<connector ID>"
    service_type: "mongodb"
    api_key: "<optional, generated API key>"

This UI is not saying that the connectors process isn't running, but that no process that is eligible to manage this specific connector is running.

See step 2 here: Running from a Docker container | Enterprise Search documentation [8.14] | Elastic

3

It is working now, service_type in the config.yml needed to be "mongodb" not "mongo".

I did "mongo" because in the docs

it is "mongo" for the api, but not config, my mistake.

4

Ah sorry about that. Are you using Kibana? It should have given you a code block to copy-paste directly. I'd love to have any feedback you can provide on why this wasn't straightforward, or where you would have liked to see more/different information.

Also, thanks for flagging. I bet those API examples are typoed. It should be mongodb.

5

The Kibana example config also has mongo as service type

image
image1040×333 17.3 KB

6

Oh now that hurts. :sob:
Thank you. We'll get all these fixed. Sorry for the inconvenience.

7

The Kibana example config also has mongo as service type

This Kibana example config uses the service_type that was provided in the create connector API call. When creating a MongoDB connector entirely via the UI, the service type is correctly set to mongodb.

Just clarifying that the bug is limited to the documentation and not the logic in Kibana. Fix incoming :slight_smile: