# 🎛️ Monitoring streams

- [Job Statuses](/monitoring-streams/job-and-event-statuses.md): This page outlines the status structure for Jobs & Events
- [Event Statuses](/monitoring-streams/event-statuses.md)
- [Resending data](/monitoring-streams/resending-data.md)
- [Replicate Job](/monitoring-streams/resending-data/replicate-job.md): Create a new Job using the Job data for an existing Job. Powerful when a Job containing multiple Events has failed.
- [Replicate Event](/monitoring-streams/resending-data/replicate-event.md): Create a new Event using an existing payload-in. Powerful when you want to edit the payload-in due to faulty data entry in the Source system, such as faulty postcodes or invalid characters.
- [Replicate Event without Event in Control Panel](/monitoring-streams/resending-data/replicate-event-without-event-in-control-panel.md): Replicate an Event that cannot be found directly from the Control Panel
- [Reporting](/monitoring-streams/reporting.md): Data available from the control panel.
- [Jobs](/monitoring-streams/reporting/jobs.md): Starting the process of moving data.
- [Events](/monitoring-streams/reporting/events.md)
- [Entities](/monitoring-streams/reporting/entities.md): Individual data entity tracking.
- [Alerts](/monitoring-streams/alerts.md): This section specifies why the alerting service is important and how it is structured
