Event Pipeline

Pipeline components

Each row is one container running one SeisComP process. State comes from the heartbeat that the process supervisor writes, so a module that has exited shows as unhealthy even while its container is up.

Replay

Origin time (UTC)MagnitudeLatitude LongitudeDepth (km)Phases RMS (s)Gap (°)MethodEvent

Changes are proposed here and applied by the separate configuration service, which re-validates every edit, backs up each file it touches, and restarts only the affected module. Parameters that control wiring, credentials, or filesystem paths are shown but not editable.