# Track every detail of your data ingestion

> Monitor jobs, investigate failures, and get alerted the moment something breaks. Erathos gives you full visibility into your ingestion pipelines so problems get caught and fixed fast.

Source: https://www.erathos.com/en/observability
Em português: https://www.erathos.com/observability

## One consolidated table for every ingestion pipeline.

Each job shows the operational details that matter: run status, frequency, volume processed, and recent activity.

### See only what matters

Choose which metrics show up on the jobs screen — connection, recent runs, frequency, sync type — based on what your team actually needs to track.

### Spot failures fast

Hover over recent runs to see the error reason instantly, without opening the job.

### Details one click away

Get detailed information on every run and job without leaving the screen.

## Every job run is logged and ready to inspect.

The runs screen lists every execution in a table, so you can dig into the details without leaving the page.

### Full run history

See the complete run history for every pipeline.

### Customize your view

Choose which columns show up on the runs screen — connection, trigger, rows processed, status — based on what you need to track.

### Investigate failures fast

See the full error and run details right in the drawer, no external logs needed.

## Production ingestion jobs need immediate visibility when something goes wrong.

Erathos sends alerts straight to the channels your team already uses.

### Full context in every alert

The notification arrives with the job, the error, and the duration already included — no need to open the tool to understand what happened.

### Rerun without leaving Slack or Discord

Run the job again directly from the notification, without opening Erathos.

### Mute repeated alerts

Mute a specific alert directly from the notification, without opening Erathos.

## Frequently Asked Questions

### What does it mean to have observability over data ingestion?

It means being able to see what's happening inside each pipeline, not just whether the data arrived at the destination. It involves monitoring every job in one consolidated table, investigating each run in detail, and getting alerted the moment something fails.

### Why does observability over data ingestion matter?

Because ingestion problems rarely show up right away. Pipelines fail silently, APIs return unexpected responses, and most teams only notice when dashboards stop updating. With observability, you catch and fix the problem before it turns into a bigger incident.

### How does Erathos give me this observability in practice?

With a consolidated jobs screen, a complete run history with a details drawer, and alerts sent straight to Slack, Discord, or email whenever a job fails.

### Does more observability mean more setup work?

Not necessarily. The jobs and runs screens come ready to use, and alerts are configured once per channel. You only make changes when you want to adjust who receives what.

### How do I keep track of this day to day, without opening the settings all the time?

Every run is logged with its status, duration, and volume processed. When something fails, the alert reaches the right channel automatically, with no need to check manually.