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

Provide contextual process data in logging context

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.12.0, 7.12.0-alpha5
    • None
    • None
    • None

      • Diagnostic context is set during process execution (e.g. in PVM)
      • The diagnostic context is cleared when the execution context is successfully left (e.g. activity finishes)
      • When an exception is thrown, the context is not cleared (so subsequent exception logging can use the context => command context close and job executor), and it is only cleared after that
      • Context is set as MDC context in SLF4J (=> research what happens if an slf4j implementation does not implement MDC)

      Contextual data:

      • Process definition id
      • Process instance id
      • Activity id
      • Process application name
      • Business Key
      • Tenant id

        This is the controller panel for Smart Panels app

          1. initial_brainstorming.jpg
            initial_brainstorming.jpg
            2.04 MB

            [CAM-10798] Provide contextual process data in logging context

            Tobias Metzke-Bernstein added a comment - - edited

            Decisions:

            • all properties but businessKey will be enabled by default with reasonable names in the MDC (e.g. "activityId", "processInstanceId", ...)
            • businessKey will not be enabled by default because it might introduce a lookup for the processInstance which we don't want to impose by default
            • a property can be enabled by setting/overriding its context name in the engine configuration
            • a property can be disabled by setting its context name to "" (empty String) or null (depending on the engine configuration option chosen)

            Tobias Metzke-Bernstein added a comment - - edited Decisions: all properties but businessKey will be enabled by default with reasonable names in the MDC (e.g. "activityId", "processInstanceId", ...) businessKey will not be enabled by default because it might introduce a lookup for the processInstance which we don't want to impose by default a property can be enabled by setting/overriding its context name in the engine configuration a property can be disabled by setting its context name to "" (empty String) or null (depending on the engine configuration option chosen)

              nikola.koevski Nikola Koevski
              thorben.lindhauer Thorben Lindhauer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: