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.

Sign up for GitHub

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

Jump to bottom

Playbook: Use component name in "Last execution traces" #8352

Closed
romain-filigran opened this issue Sep 16, 2024 · 0 comments · Fixed by #8625
Closed

Playbook: Use component name in "Last execution traces" #8352

romain-filigran opened this issue Sep 16, 2024 · 0 comments · Fixed by #8625
Assignees
@aHenryJard
Labels
feature use for describing a new feature to develop playbook Linked to automation engine solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@romain-filigran
Copy link
Member

Use case

To debug the execution of a playbook, it would be preferable to use the “component name” specified by the end user in “Last execution traces” instead of using the “generic” component name. This is particularly important when you have a tree that uses the same component several times.

Capture d'écran 2024-09-16 082301
@romain-filigran romain-filigran added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team playbook Linked to automation engine and removed needs triage use to identify issue needing triage from Filigran Product team labels Sep 16, 2024
@aHenryJard aHenryJard self-assigned this Sep 18, 2024
aHenryJard added a commit that referenced this issue Oct 7, 2024
@aHenryJard
[backend] use component name in traces and fix warn issue.(#8352)
2c6247d
@aHenryJard aHenryJard mentioned this issue Oct 7, 2024
Merged
5 tasks
aHenryJard added a commit that referenced this issue Oct 8, 2024
@aHenryJard
[backend] use component name in traces and fix warn issue.(#8352)(#8310)
93f1a93
@aHenryJard aHenryJard added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aHenryJard aHenryJard

Labels
feature use for describing a new feature to develop playbook Linked to automation engine solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[backend] use component name in traces and fix warn issue.(#8352)(#8310) OpenCTI-Platform/opencti
2 participants
@aHenryJard @romain-filigran