Skip to main content
The Observability interface in Prophecy lets you monitor your deployed projects, review scheduled pipelines, and audit run history. You’ll be able to view all projects and pipelines that your teams own. To access, click Observability (the line graph icon) in the left sidebar.

Deployed Projects

The Deployed Projects tab in the Observability interface shows all projects that have been published to Prophecy fabrics. It lets you view details on release versions and recent execution status at the project level. For each project deployment, Prophecy provides the following information. Use the following filters to narrow the results:
When a project is published to multiple fabrics, Prophecy creates an individual project deployment for each fabric. You will see all of these deployments in the Deployed Projects page. You cannot revert or delete a project deployment.

Scheduled Pipelines

The Scheduled Pipelines tab in the Observability interface displays all pipelines configured with a schedule across environments. It provides details on pipeline execution frequency and recent run outcomes. Use this page to verify that pipelines are scheduled correctly and to identify patterns of success or failure. For each scheduled pipeline, Prophecy provides the following information.
You may see multiple rows for the same pipeline if the parent project is deployed to multiple fabrics.
Use the following filters to narrow the results:

Run History

Use the Run History tab in the Observability interface to view and analyze recent pipeline runs across all fabrics and projects. This page provides detailed metadata for each run, including its type, duration, status, and execution context. You can also use Run History to open historical runtime logs and inspect previous pipeline executions in Historical Mode. Use the following filters to narrow the results. For each historical pipeline run, Prophecy provides the following information. To see who or what triggered a run, click the Run details icon at the end of the row. See View run details.

Run statuses

Stop a run

To stop a run that’s in progress:
  1. In the Status column of the run, click the Stop run icon.
  2. Click Stop run to confirm.
Prophecy discards any work in progress and marks the run as Cancelled. If the run finishes before Prophecy can stop it, Prophecy tells you that the run already finished.

Restart a scheduled run

You can restart a scheduled run that failed, finished with warnings, or was cancelled. The restart uses the schedule’s current version and parameters. To restart a run:
  1. In the Status column of the run, click the Restart run icon.
  2. Click Restart run to confirm.
The restart appears in Run History as a new attempt of the original run. You can only restart the latest attempt.

View run details

Click the Run details icon at the end of a row to open the run details panel. The panel shows the run ID, which you can copy, and the run status. It also includes the following sections. Click a linked run ID to open the details of that run. Click the back arrow to return to the previous run. The Run details icon doesn’t appear for older runs that don’t have this information.

Open historical runtime logs

You can inspect completed pipeline executions directly from the Run History table. To open historical runtime logs:
  1. Open the Run History tab and locate the run you want to inspect.
  2. In the Logs column, click See logs.
Open historical runtime logs Prophecy opens the selected pipeline in Historical Mode, restoring:
  • Runtime logs for the selected execution
  • The historical pipeline snapshot
  • Component execution statuses and progress information
In Historical Mode, the pipeline canvas becomes read-only so you can safely review the historical execution context without modifying the current pipeline version.
Historical runtime logs and pipeline snapshots are retained for a limited period of time and may not be available for every historical run.
For more information about runtime logs, Historical Mode, and pipeline snapshots, see Runtime logs.