/Monitoring_Backend_Microservices

Primary LanguageTypeScript

SOLUTION VIDEO BY ME

MONOTORING_SERVICE.mp4

Log Ingestor and Query Interface

Objective

Develop a log ingestor system that can efficiently handle vast volumes of log data, and offer a simple interface for querying this data using full-text search or specific field filters.

Both the systems (the log ingestor and the query interface) can be built using any programming language of your choice.The logs should be ingested (in the log ingestor) over HTTP, on port 3000

Flow Diagram

MONOTORING_SERVICE

Inserting data to datbase using Redis as PUB-SUB

image

Sample Log Data Format:

The logs to be ingested will be sent in this format

{
 "level": "error",
 "message": "Failed to connect to DB",
 "resourceId": "server-1234",
 "timestamp": "2023-09-15T08:00:00Z",
 "traceId": "abc-xyz-123",
 "spanId": "span-456",
 "commit": "5e5342f",
 "metadata": {
  "parentResourceId": "server-0987"
 }
}

Requirements

The requirements for the log ingestor and the query interface are specified below.

Log Ingestor:

  • Develop a mechanism to ingest logs in the provided format.
  • Ensure scalability to handle high volumes of logs efficiently.
  • Mitigate potential bottlenecks such as I/O operations, database write speeds, etc.
  • Make sure that the logs are ingested via an HTTP server, which runs on port 3000 by default.

Query Interface:

  • Offer a user interface (Web UI or CLI) for full-text search across logs.
  • Include filters based on:
    • level
    • message
    • resourceId
    • timestamp
    • traceId
    • spanId
    • commit
    • metadata.parentResourceId
  • Aim for efficient and quick search results.

Advanced Features (Bonus):

  • Implement search within specific date ranges.
  • Utilize regular expressions for search.
  • Allow combining multiple filters.
  • Provide real-time log ingestion and searching capabilities.
  • Implement role-based access to the query interface.