Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-11275

In Cockpit, I can see the id of the activity that failed a job

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.13.0, 7.13.0-alpha3
    • None
    • engine, webapp
    • None

      AT

      I can see the id of the activity that failed a job in the runtime view and in job logs in the history view (new attribute introduced with CAM-10378).

      For these entities:

      • the failed job log
      • the runtime job
      • the runtime incident
      • the historic incident

        This is the controller panel for Smart Panels app

            [CAM-11275] In Cockpit, I can see the id of the activity that failed a job

            Additional feature request from fml2 (original creator of CAM-10378, see this comment):

            If an uncaught error occurs then there is a red circle in the process diagram. The circle marks the position where the failed job started. Additionally, it might be useful to have (another?) marker (in some other color?) that would mark the failed activity (which might be different from the job start).

            I.e. I mean the graphical representation of the process instance, not the table view of the process data.

            Tobias Metzke-Bernstein added a comment - Additional feature request from  fml2 (original creator of CAM-10378 , see  this comment ): If an uncaught error occurs then there is a red circle in the process diagram. The circle marks the position where the failed job started. Additionally, it might be useful to have (another?) marker (in some other color?) that would mark the failed activity (which might be different from the job start). I.e. I mean the graphical representation of the process instance, not the table view of the process data.

            Martin Stamm added a comment -

            Hi fml2,

            we decide to not add a graphical representation of this feature at this time. Currently, we see problems in the usability if we add another Badge to the Diagram (e.g. correlation between the incident badge and job start badge in complex diagrams, up to 4 Badges in the history view).

            Due to these concerns we will only add the information to the Table view. We might extend the diagram view in the future with more UX preparation.

            If you have any questions or concerns please let us know.

            Best Regards
            Martin

            Martin Stamm added a comment - Hi fml2 , we decide to not add a graphical representation of this feature at this time. Currently, we see problems in the usability if we add another Badge to the Diagram (e.g. correlation between the incident badge and job start badge in complex diagrams, up to 4 Badges in the history view). Due to these concerns we will only add the information to the Table view. We might extend the diagram view in the future with more UX preparation. If you have any questions or concerns please let us know. Best Regards Martin

            fml2 added a comment -

            I'm OK with your desire not to overload the digram. Maybe just a thought: would it be possible to change the background of the failed activity (e.g. make it slightly red) when I hover over the incident badge? But that's just a thought.

            fml2 added a comment - I'm OK with your desire not to overload the digram. Maybe just a thought: would it be possible to change the background of the failed activity (e.g. make it slightly red) when I hover over the incident badge? But that's just a thought.

            Martin Stamm added a comment -

            Thanks for the suggestion fml2, I already thought about highlighting them in a somehow.

            The Problem I see when hovering over batches is, that multiple incidents at one Activity might relate to different failing activities.
            From the technical side, these interactions require a more complex solution than just adding a row to a table. For this reason, I opened CAM-11404 as a follow up an will proceed with this ticket with the smaller scope for now. We will keep you updated when we schedule the follow-up

            Martin Stamm added a comment - Thanks for the suggestion fml2 , I already thought about highlighting them in a somehow. The Problem I see when hovering over batches is, that multiple incidents at one Activity might relate to different failing activities. From the technical side, these interactions require a more complex solution than just adding a row to a table. For this reason, I opened CAM-11404 as a follow up an will proceed with this ticket with the smaller scope for now. We will keep you updated when we schedule the follow-up

              martin.stamm Martin Stamm
              tobias.metzke Tobias Metzke-Bernstein
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: