Skip to main content

Introduction to Log Analysis Agent

Overview​

The Log Analysis Agent diagnoses technical failures from log output. Give it a log file (path or pasted content) and it will:

  • Identify every distinct error or exception in the log
  • Look each error up in the Syntasa Known Error Database (KEDB)
  • Return a structured report with the symptom, root cause, resolution, and workaround for each error
  • Offer to save unknown errors as new KEDB entries so the next person who hits the same issue gets an instant answer

The agent works on logs from three sources:

  • A local path on the agent host
  • A Google Cloud Storage URI/URL
  • An Amazon S3 URI/URL

Users can also paste raw log text directly into the chat.

Why the Log Analysis Agent Matters​

Troubleshooting distributed systems and enterprise workloads often requires navigating large volumes of logs, stack traces, and operational events. Identifying the real root cause manually can be slow and difficult, especially when multiple errors appear together.

The Log Analysis Agent simplifies this process by:

  • Automatically detecting failures
  • Matching known issues against the KEDB
  • Providing actionable remediation guidance
  • Reducing repetitive operational investigations

This enables faster diagnosis and more consistent operational support.

When to Use the Log Analysis Agent​

The Log Analysis Agent is designed specifically for operational troubleshooting scenarios. Recommended use cases include:

  • An application failed and you have the log but don't know what broke
  • You want to know if an error has been seen before and how it was fixed
  • You need a report you can paste into a ticket, with severity and the affected component already classified

When Not to Use It​

The Log Analysis Agent is not intended for general platform guidance or documentation questions.

Do not use it for:

  • General questions about the Syntasa platform
  • Platform how-to guidance
  • Documentation lookups
  • Feature explanations

For these topics, users should instead use the Syntasa Help Agent.

Supported Log Sources​

The agent supports multiple input methods to accommodate different operational environments.

Local File Paths​

Example:

/var/log/syntasa/job-78321.log

Google Cloud Storage​

Example:

gs://syntasa-prod-logs/ingest/2026-05-08/run.log

Amazon S3​

Example:

s3://customer-logs/etl-failed-2026-05-07.log

Raw Log Text​

Users can also directly paste stack traces and log blocks into the chat interface.

Key Benefits​

Faster Root Cause Analysis​

The agent identifies distinct errors and correlates them with known fixes from the KEDB.

Consistent Operational Guidance​

Structured reports provide standardized troubleshooting outputs across teams.

Knowledge Reuse​

Unknown issues can be saved into the KEDB, improving future operational efficiency.

Simplified Incident Documentation​

Generated reports can be reused directly in operational tickets and escalation workflows.

Conclusion​

The Log Analysis Agent provides a focused and efficient approach to operational troubleshooting by transforming raw logs into structured diagnostic insights. By integrating directly with the Syntasa Known Error Database, it helps organizations reduce investigation time, improve operational consistency, and accelerate issue resolution.