-
Notifications
You must be signed in to change notification settings - Fork 0
ResidentLogHandler
A resident handler runs within the Executor scope. For Kubernetes the operation will run within the same pod and same Docker image as the Executor. Whereas Handlers are run as separate pods / images and have their own memory & CPU constraints.
Note: Be mindful of memory & CPU constraints when deploying your Executor pod
The Log handler is simply logs a configured message.
A workflow has some operation output that the customer wants to log for debugging and/or dashboards.
Field | Type | Notes |
---|---|---|
payload | Object | |
.logMessages | String[] | Messages to log allowing variable referencing |
Creates a logger line for each string in logMessages array.
{
"payload": {
"logMessages": [
"operationType=logHandler operationName=analysis bitrate=@<mediaInfo.1.out::/inputStreams/video/0/params/bitrate> duration=@<mediaInfo.1.out::/inputStreams/video/0/params/duration> externalFileId=@<mediaInfo.1.out::/inputs/0/params/externalFileId>"
]
}
- Submission
- Scheduling
-
Execution
the ResourcePool
Agenda
the workflow
Agenda Template
the workflow definition
Customer
Insight
the scheduling queue definition
Operation Progress
the state of the running Agenda operations
Progress
the state of the running Agendas
ResourcePool
the processing resources
Agenda Service
the workflow submission
Progress Service
rolled up agenda progress summary
ResourcePool Service
getting work and updating progress
AgendaReclaimer
restarting stuck Agendas
AgendaRetry
retrying failed Agendas
DataObjectReaper
reaping expired data objects
PodReaper
reaping stuck Kubernetes pods