Skip to content
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

[🐛 Bug]: workflow log not visualized #3004

Open
00041275 opened this issue Jan 9, 2025 · 3 comments
Open

[🐛 Bug]: workflow log not visualized #3004

00041275 opened this issue Jan 9, 2025 · 3 comments
Labels
Bug Something isn't working

Comments

@00041275
Copy link
Contributor

00041275 commented Jan 9, 2025

workflow log not visualized, but data has in DB

image

@00041275 00041275 changed the title [🐛 Bug]: [🐛 Bug]: workflow log not visualized Jan 9, 2025
Copy link

dosubot bot commented Jan 9, 2025

The issue you're experiencing with the workflow log not being visualized, despite data being present in the database, could be due to several factors:

  1. Environment Variable Configuration: Ensure that the KEEP_STORE_WORKFLOW_LOGS environment variable is set to "true". This setting is necessary for logs to be stored in the database [1].

  2. Handler Initialization: Verify that the WorkflowDBHandler is properly initialized and attached to the logger. If not, logs will not be captured and pushed to the database [1].

  3. Database Push Failure: Check for any errors during the execution of push_logs_to_db, such as database connection issues or session commit failures, which could prevent logs from being stored [1].

  4. Log Record Attributes: Ensure that log records have the required attributes, like workflow_execution_id, for them to be processed by the emit method [1].

  5. Visualization Layer: There might be issues in the visualization layer or application that retrieves and displays these logs, even if they are present in the database [1].

Regarding the "AttributeError" during the "dismiss-alert" action, common causes include missing provider types or configurations in the workflow definition. Ensure that the provider is properly defined and contains all necessary attributes [2].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot dosubot bot added the Bug Something isn't working label Jan 9, 2025
@shahargl
Copy link
Member

@00041275 “data has in DB” you mean you see the logs in the DB? Is there any request from the frontend that fails? Specifically to /workflow/{id}/logs?

@00041275
Copy link
Contributor Author

@00041275 “data has in DB” you mean you see the logs in the DB? Is there any request from the frontend that fails? Specifically to /workflow/{id}/logs?

I will check it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants