Data Processing

Structured Log Analyzer

Detect common log formats, extract core fields, infer field types, and export parsed logs as JSON, CSV, or SQL inserts

html· HTML resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/structured-log-analyzer' \
  -F 'file=@/path/to/logFile.ext'

# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/structured-log-analyzer' \
  -F 'logInput={"level":"error","service":"billing","message":"Charge failed"}
Mar 10 14:03:02 host app[123]: INFO Worker started' \
  -F 'logFile=/path/to/file.ext' \
  -F 'exportFormat=csv' \
  -F 'aggregateMultiline=true' \
  -F 'customRegex=^(?<timestamp>\S+) (?<level>\w+) (?<source>\w+) (?<message>.+)$'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/structured-log-analyzer

Parameters

Name	Type	Required	Description
logInput	textarea	No	—
logFile	fileupload required	No	—
exportFormat	select	No	—
aggregateMultiline	checkbox	No	—
customRegex	text	No	—

File-type parameters must be uploaded first via POST /upload/structured-log-analyzer, then the returned filePath is passed to the corresponding file field.

Response format

HTML result

JSON

{
  "result": "<div>Processed HTML content</div>",
  "error": "Error message (optional)",
  "message": "Notification message (optional)",
  "metadata": {
    "key": "value"
  }
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-structured-log-analyzer": {
      "name": "structured-log-analyzer",
      "description": "Detect common log formats, extract core fields, infer field types, and export parsed logs as JSON, CSV, or SQL inserts",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=structured-log-analyzer",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "structured-log-analyzer",
    "arguments": {
  "logInput": "{\"level\":\"error\",\"service\":\"billing\",\"message\":\"Charge failed\"}\nMar 10 14:03:02 host app[123]: INFO Worker started",
  "logFile": "https://example.com/file.ext",
  "exportFormat": "csv",
  "aggregateMultiline": true,
  "customRegex": "^(?<timestamp>\\S+) (?<level>\\w+) (?<source>\\w+) (?<message>.+)$"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]