A guide on Event's observability and monitoring layer that gives instant visibility into job states, transaction data and log history
The 3 main pillars of Event's enterprise-level observability and visibility layer are:
- 2.Logs and
In the context of event orchestration and state management, a "job" typically refers to a self-contained unit of work that is scheduled or processed as part of a larger workflow or business process.
In the context of Event, the Job manages the state of the process defined by your Pipeline. Ultimately, it encompasses a range of tasks such as computations, data processing, resource allocation, and interactions with other systems or services.
Once a Pipeline is triggered, it will create an active Job. A Job has associated state information, including:
- Job state: Indicates the current stage of the Job
- Job result: Contains the output of the job, if any. This could be a computation result, a data transformation output, or an indicator of success or failure.
- Job metadata: Other information about the job, such as its priority, creation time, start time, end time, or the identity of the user or system that initiated it.
In Event, Jobs and their states are automatically managed and executed by the orchestrator.
A Job can be in one of the following states:
You're always a few clicks away from getting a real-time view into the state and progress of a Pipeline's active Jobs.
To view Jobs:
Step 1: Go to the Pipeline tab of the Developer Dashboard
Step 2: Click on an existing Pipeline to open it
Step 3: Click the Jobs tab
The Event architecture and ecosystem is entirely comprised of immutable Transactions, which guarantees uniqueness and idempotency.
To view a Transaction:
Step 1: Go to the Live Events tab of the Developer Dashboard
Step 2: Click on an
acknowledgedevent to open it
Step 3: Click the Transactions tab