Machine learning anomaly detection in Elasticsearch - Time & Space Complexity

Time Complexity: Machine learning anomaly detection

O(n)

Understanding Time Complexity

When using machine learning for anomaly detection in Elasticsearch, it is important to understand how the time taken grows as the data size increases.

We want to know how the processing time changes when we analyze more data points.

Scenario Under Consideration

Analyze the time complexity of the following Elasticsearch anomaly detection job configuration.

POST _ml/anomaly_detectors/job_id/_start
{
  "datafeed_config": {
    "indices": ["logs"],
    "query": { "match_all": {} }
  },
  "analysis_config": {
    "bucket_span": "15m",
    "detectors": [{ "function": "mean", "field_name": "response_time" }]
  }
}
    

This code starts an anomaly detection job that scans all log entries to find unusual average response times in 15-minute buckets.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning and aggregating data points in fixed time buckets.
• How many times: Once per bucket, covering all data points in that bucket.

How Execution Grows With Input

As the number of data points grows, the job processes more buckets or more points per bucket.

Input Size (n)	Approx. Operations
10,000 data points	~10,000 operations (each point processed once)
100,000 data points	~100,000 operations
1,000,000 data points	~1,000,000 operations

Pattern observation: The operations grow roughly in direct proportion to the number of data points.

Final Time Complexity

Time Complexity: O(n)

This means the time to detect anomalies grows linearly with the number of data points analyzed.

Common Mistake

[X] Wrong: "The anomaly detection runs instantly no matter how much data there is."

[OK] Correct: The job must look at each data point to find unusual patterns, so more data means more work and more time.

Interview Connect

Understanding how data size affects machine learning tasks like anomaly detection helps you explain system behavior and design efficient solutions.

Self-Check

"What if we changed the bucket span from 15 minutes to 1 minute? How would the time complexity change?"

Practice

1. What is the main purpose of machine learning anomaly detection in Elasticsearch?

easy

A. To automatically find unusual patterns in data

B. To store large amounts of data efficiently

C. To create visual dashboards for data

D. To backup Elasticsearch clusters

Solution

1. Step 1: Understand anomaly detection goal

   Machine learning anomaly detection is designed to find unusual or unexpected patterns in data automatically.

2. Step 2: Compare options with purpose

   Options B, C, and D describe other Elasticsearch features, not anomaly detection.

3. Final Answer:

   To automatically find unusual patterns in data -> Option A

4. Quick Check:

   Purpose of anomaly detection = find unusual patterns [OK]

Hint: Anomaly detection finds unusual data automatically [OK]

Common Mistakes:

• Confusing anomaly detection with data storage
• Thinking anomaly detection creates dashboards
• Mixing anomaly detection with backup tasks

2. Which Elasticsearch API call starts the anomaly detection process by feeding data to the job?

easy

A. POST _ml/anomaly_detectors/<job_id>/_start_datafeed

B. GET _ml/anomaly_detectors/<job_id>/results

C. PUT _ml/anomaly_detectors/<job_id>

D. DELETE _ml/anomaly_detectors/<job_id>

Solution

1. Step 1: Identify datafeed start API

   The API to start feeding data to an anomaly detection job is POST _ml/anomaly_detectors/<job_id>/_start_datafeed.

2. Step 2: Eliminate other options

   GET retrieves results, PUT creates or updates jobs, DELETE removes jobs.

3. Final Answer:

   POST _ml/anomaly_detectors/<job_id>/_start_datafeed -> Option A

4. Quick Check:

   Start datafeed = POST _start_datafeed [OK]

Hint: Start datafeed uses POST with _start_datafeed endpoint [OK]

Common Mistakes:

• Using GET instead of POST to start datafeed
• Confusing job creation with starting datafeed
• Deleting job instead of starting datafeed

3. Given this Elasticsearch ML job result snippet:

{"job_id":"sales_anomaly","results":[{"timestamp":1680000000000,"anomaly_score":75},{"timestamp":1680003600000,"anomaly_score":5}]}

Which timestamp shows a likely anomaly?

medium

A. Neither timestamp

B. 1680003600000

C. Both timestamps

D. 1680000000000

Solution

1. Step 1: Understand anomaly score meaning

   Higher anomaly scores indicate more unusual data points. A score of 75 is high, 5 is low.

2. Step 2: Identify timestamp with high score

   The timestamp 1680000000000 has anomaly_score 75, indicating a likely anomaly.

3. Final Answer:

   1680000000000 -> Option D

4. Quick Check:

   High anomaly score = likely anomaly [OK]

Hint: Higher anomaly_score means more likely anomaly [OK]

Common Mistakes:

• Choosing low anomaly score as anomaly
• Selecting both timestamps without checking scores
• Ignoring anomaly_score values

4. You created an anomaly detection job but see no results after starting the datafeed. What is a likely cause?

medium

A. The job was deleted before starting

B. The Elasticsearch cluster is offline

C. The datafeed is not running or has stopped

D. The anomaly scores are all zero

Solution

1. Step 1: Check datafeed status

   If no results appear, the datafeed may not be running or has stopped feeding data to the job.

2. Step 2: Evaluate other options

   Job deletion would prevent starting datafeed; cluster offline causes broader failures; zero scores still produce results.

3. Final Answer:

   The datafeed is not running or has stopped -> Option C

4. Quick Check:

   No results usually mean datafeed stopped [OK]

Hint: No results? Check if datafeed is running [OK]

Common Mistakes:

• Assuming zero scores mean no results
• Ignoring datafeed status
• Blaming cluster offline without checking datafeed

5. You want to detect unusual spikes in website traffic using Elasticsearch ML anomaly detection. Which steps should you follow to set this up correctly?

hard

A. Backup traffic data, create index pattern, then visualize spikes

B. Create a job with traffic data, start datafeed, then analyze anomaly results

C. Create a dashboard, upload traffic logs, then run anomaly detection manually

D. Delete old data, create job without datafeed, then check results

Solution

1. Step 1: Create ML job with traffic data

   Define an anomaly detection job using the website traffic data to analyze patterns.

2. Step 2: Start the datafeed to feed data into the job

   Start the datafeed so the job can process incoming traffic data continuously.

3. Step 3: Analyze the anomaly detection results

   Review the results to identify unusual spikes or anomalies in traffic.

4. Final Answer:

   Create a job with traffic data, start datafeed, then analyze anomaly results -> Option B

5. Quick Check:

   Job + datafeed + analyze = correct setup [OK]

Hint: Job creation + datafeed start + result check = setup [OK]

Common Mistakes:

• Skipping datafeed start step
• Confusing dashboards with anomaly detection setup
• Deleting data before analysis