As a part of the ongoing Transformation API overhaul we've changed transformation events. We tried to keep it simple, so there's one event for each:
- Engine startup
- Start of a phase
- Database cleanup (happens at the beginning and end of a phase)
- Input mapping
- Input mapping that takes longer than 120s (configurable)
- Transformation (as a whole, not a query in the transformation)
- Query that takes longer than 120s (configurable)
- Output mapping
- Engine shutdown (success or error)
There are no more any START or END events and the engine produces less events. Further activity can be found in related storage events or jobs (eg. table imports and exports).