Kibana setup and connection in Elasticsearch - Time & Space Complexity

Time Complexity: Kibana setup and connection

O(n)

Understanding Time Complexity

When setting up Kibana and connecting it to Elasticsearch, it's important to understand how the time to establish this connection grows as the system scales.

We want to know how the connection process behaves when more data or nodes are involved.

Scenario Under Consideration

Analyze the time complexity of the following Elasticsearch connection setup in Kibana.

PUT /_cluster/settings
{
  "persistent": {
    "cluster.routing.allocation.enable": "all"
  }
}

GET /_cluster/health?wait_for_status=green&timeout=30s
    

This snippet sets cluster routing and waits for the cluster to be healthy before Kibana connects.

Identify Repeating Operations

Look for repeated checks or polling during connection setup.

• Primary operation: Polling the cluster health status repeatedly until green.
• How many times: Depends on cluster size and health; each poll checks all nodes.

How Execution Grows With Input

As the number of nodes or shards increases, each health check inspects more components.

Input Size (nodes/shards)	Approx. Operations
10	Checks 10 nodes/shards per poll
100	Checks 100 nodes/shards per poll
1000	Checks 1000 nodes/shards per poll

Pattern observation: The work grows roughly in direct proportion to the number of nodes or shards.

Final Time Complexity

Time Complexity: O(n)

This means the time to check cluster health grows linearly with the number of nodes or shards.

Common Mistake

[X] Wrong: "The connection time stays the same no matter how big the cluster is."

[OK] Correct: Each health check must look at every node or shard, so more nodes mean more work and longer checks.

Interview Connect

Understanding how connection and health checks scale helps you explain system responsiveness and reliability in real projects.

Self-Check

What if Kibana used cached health info instead of polling every time? How would the time complexity change?

Practice

1. What is the main requirement before starting Kibana to ensure it works properly?

easy

A. The browser must be Internet Explorer

B. Kibana must be installed on a different server

C. Elasticsearch must be running

D. A database connection must be configured

Solution

1. Step 1: Understand Kibana's dependency

   Kibana is a visualization tool that requires Elasticsearch to provide data.

2. Step 2: Confirm service requirement

   Without Elasticsearch running, Kibana cannot fetch or display data.

3. Final Answer:

   Elasticsearch must be running -> Option C

4. Quick Check:

   Kibana needs Elasticsearch running [OK]

Hint: Remember: Kibana shows data from Elasticsearch only [OK]

Common Mistakes:

• Thinking Kibana works standalone without Elasticsearch
• Confusing Kibana with a database
• Assuming any browser works without checking compatibility

2. Which setting in kibana.yml specifies the Elasticsearch server address?

easy

A. elasticsearch.hosts

B. server.port

C. kibana.index

D. logging.dest

Solution

1. Step 1: Identify configuration purpose

   The kibana.yml file configures Kibana settings including connection details.

2. Step 2: Locate Elasticsearch host setting

   The setting elasticsearch.hosts defines the URL(s) of Elasticsearch nodes Kibana connects to.

3. Final Answer:

   elasticsearch.hosts -> Option A

4. Quick Check:

   Elasticsearch server address = elasticsearch.hosts [OK]

Hint: Look for 'elasticsearch.hosts' in kibana.yml [OK]

Common Mistakes:

• Confusing server.port with Elasticsearch address
• Using kibana.index which is for saved objects
• Mistaking logging.dest for connection settings

3. Given the following kibana.yml snippet:

elasticsearch.hosts: ["http://localhost:9200"]
server.port: 5601

What URL should you open in your browser to access Kibana?

medium

A. http://localhost:9200

B. http://localhost:9200/kibana

C. http://localhost:5601/elasticsearch

D. http://localhost:5601

Solution

1. Step 1: Identify Kibana server port

   The setting server.port: 5601 means Kibana listens on port 5601.

2. Step 2: Determine correct URL

   To access Kibana, open the browser at http://localhost:5601. Port 9200 is for Elasticsearch, not Kibana.

3. Final Answer:

   http://localhost:5601 -> Option D

4. Quick Check:

   Kibana URL uses server.port = 5601 [OK]

Hint: Kibana runs on server.port, default 5601 [OK]

Common Mistakes:

• Opening Elasticsearch port 9200 instead of Kibana port
• Appending /kibana or /elasticsearch incorrectly
• Confusing ports between services

4. You started Kibana but get a connection error. Which of these is the most likely cause?

medium

A. Elasticsearch service is not running

B. Kibana is running on port 9200

C. Browser cache is full

D. Kibana.yml file is missing

Solution

1. Step 1: Understand connection error cause

   Kibana depends on Elasticsearch; if Elasticsearch is down, Kibana cannot connect.

2. Step 2: Evaluate other options

   Kibana does not run on port 9200 (Elasticsearch default). Browser cache or missing config file usually cause different errors.

3. Final Answer:

   Elasticsearch service is not running -> Option A

4. Quick Check:

   Connection error = Elasticsearch down [OK]

Hint: Check Elasticsearch service status first [OK]

Common Mistakes:

• Assuming Kibana runs on Elasticsearch port
• Blaming browser cache for connection errors
• Ignoring Elasticsearch service status

5. You want to connect Kibana to a remote Elasticsearch server at http://192.168.1.100:9200. Which is the correct elasticsearch.hosts setting in kibana.yml?

hard

A. elasticsearch.hosts: ["http://localhost:9200"]

B. elasticsearch.hosts: ["http://192.168.1.100:9200"]

C. elasticsearch.hosts: "192.168.1.100:5601"

D. elasticsearch.hosts: ["https://192.168.1.100:5601"]

Solution

1. Step 1: Identify remote Elasticsearch URL

   The remote server address is http://192.168.1.100:9200, which is the default Elasticsearch port.

2. Step 2: Set elasticsearch.hosts correctly

   The setting must be a list with the full URL including protocol and port: ["http://192.168.1.100:9200"].

3. Step 3: Eliminate incorrect options

   elasticsearch.hosts: ["http://localhost:9200"] points to localhost, not remote. Options C and D use wrong ports or protocols for Elasticsearch.

4. Final Answer:

   elasticsearch.hosts: ["http://192.168.1.100:9200"] -> Option B

5. Quick Check:

   Remote Elasticsearch URL in elasticsearch.hosts list [OK]

Hint: Use full URL with http and port 9200 in elasticsearch.hosts [OK]

Common Mistakes:

• Using localhost instead of remote IP
• Omitting protocol (http://)
• Using wrong port like 5601 for Elasticsearch