EKS Log Analyzer

Provides automated analysis of Amazon EKS node logs by cross-checking tar logs and offering workflow-guided troubleshooting.

python

0

GitHub Stars

python

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "dksshddl-eks-log-mcp": {
      "command": "python",
      "args": [
        "/path/to/eks-log-mcp/server.py"
      ]
    }
  }
}

You can connect this MCP server to an MCP client to automatically analyze Amazon EKS node logs. It collects and analyzes tar logs from the EKS Log Collector, provides component-specific analysis tools, and offers troubleshooting workflows to help you diagnose issues efficiently.

How to use

You will connect your MCP client to this server using the MCP configuration. Once connected, your AI assistant can trigger the available analysis tools to inspect EKS log sets, navigate through the structured log layout, and apply workflow-guided diagnostics for VPC CNI, kubelet, DNS, networking, and more.

How to install

Prerequisites: You need Python and pip installed on your system.

cd eks-log-mcp
pip install -r requirements.txt

MCP configuration

Configure the MCP client to connect to this server using the following stdio configuration. This example runs the MCP server locally via Python and points to the server script path you provide.

{
  "mcpServers": {
    "eks_log_analyzer": {
      "command": "python",
      "args": ["/path/to/eks-log-mcp/server.py"]
    }
  }
}

Usage tips

Use the commands below to interact with the analyzer once the MCP server is running and connected through your client. These examples illustrate the flow and common actions you will perform.

# Example usage patterns (high level):
# 1) Upload or point to an extracted EKS log tar
extract_eks_logs(tar_path="path/to/eks_logs.tar.gz")

# 2) Inspect node information
get_node_info(log_dir="path/to/eks_logs")

# 3) Run a targeted analysis, e.g., VPC CNI
analyze_vpc_cni(log_dir="path/to/eks_logs")

# 4) Search for errors across all logs
search_logs(log_dir="path/to/eks_logs", pattern="error")

Hardware and runtime notes

This MCP server is designed to work with the EKS Log Collector outputs and expects a tar archive structure as the input. Ensure your tar files contain the supported log directories such as kernel, system, containerd, storage, var_log, networking, ipamd, kubelet, and cni.

Available tools

extract_eks_logs

Unpacks the EKS log collector tar file to prepare it for analysis.

list_structure

Displays the log directory structure to help you navigate the extracted logs.

get_node_info

Retrieves basic node information such as instance-id, region, and kernel details.

analyze_vpc_cni

Analyzes VPC CNI logs including aws-routed-eni, ipamd, and CNI settings.

analyze_kubelet

Analyzes kubelet logs and configuration for potential issues.

analyze_containerd

Analyzes containerd logs and configuration.

analyze_dns

Performs a four-step DNS troubleshooting analysis.

analyze_node_join

Investigates Node Join and NotReady issues.

analyze_networking

Analyzes networking components including iptables, conntrack, routes, and ebpf.

analyze_network_policy

Analyzes Network Policy using eBPF-based insights.

analyze_storage

Examines storage configuration and mounts (fstab, lsblk, mounts).

analyze_system

Provides system-level analysis using ps, netstat, and dmesg.

analyze_pod_logs

Analyzes logs for specific pods such as kube-proxy and aws-node.

search_logs

Searches across all logs for specified patterns.