-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
celery jobs should generate recordings #361
Comments
TitleEnable AppMap Recording for Celery Jobs ProblemCurrently, when a Celery job runs in the application, it does not generate AppMap recordings. This behavior results in a lack of visibility into the execution and performance of tasks managed by Celery, which impedes the ability to trace issues or optimize task handling. AnalysisTo enable AppMap recording for Celery jobs, we need to integrate the AppMap recorder into the task execution lifecycle of Celery. Celery tasks go through a specific sequence of states: pending, started, and success (or failure). By hooking into these states, we can start a recording before the task executes and stop the recording once the task completes, successfully or otherwise. We will extend the Celery task class to include AppMap recording functionality. This involves importing the AppMap recorder, starting the recording upon task initiation, and stopping it upon task completion or failure. The recorded AppMap data should be saved in a specified directory, similarly to how request recordings are handled. Proposed Changes
Detailed File Changes
By implementing these changes, Celery tasks will each generate their own AppMap recording, capturing execution details and improving observability for Celery-managed tasks. |
Each time a celery job runs it should generate AppMap data (analogous to the way a request recording gets generated).
The text was updated successfully, but these errors were encountered: