Date: Thu, 28 Mar 2024 23:06:19 +0000 (UTC) Message-ID: <1147555794.27.1711667179488@3eb09c3942ce> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_26_1582866192.1711667179487" ------=_Part_26_1582866192.1711667179487 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Until 1.0.12 you could download your l= ogs from = Troubleshooting and Support page under JMWE administration pages. From = 1.0.13 onwards you can view and download them in the JMWE Logs page.
By default, events with a level below INFO ar= e not stored and therefore cannot be included in the logs downloaded or v= iewed in the table below. However, for troubleshooting purposes, it = is possible to temporarily increase the amount of logging by changing the m= inimum level. The new level set here will remain for one hour, and will the= reafter revert to the default level, i.e. the INFO le= vel.
To set a temporary log level:
Temporary log level
drop-downApply
.Click on Reset
to revert the log level to the def=
ault INFO level.
You can also monitor your JMWE errors = and warnings related to post-functions an= d actions on your own applications by configuring a webhook.&nb= sp;
To configure a webhook:
When an error is thrown, the webhook w= ill post the error data in real time.
See the example below to understand= how to interpret the raw content.
By d=
efault, the Last day logs with a level higher than INFO ar=
e displayed in the table. You can filter the logs based on when they were c=
reated - When and the Log level - Level.&=
nbsp;To filter them further, click on More filters
to add the =
below additional filters:
You = can filter log events based on the;
Clic=
k on Apply filters
to filter the logs
Timestamp, Level, Post-function, Message Type
and Message
. And if that isn't sufficient enough to debug =
your problem you need to click on > of a log entry to s=
ee the following information:
add to filters
link.See the examples below to understand how to filter and analyze the logs.
Follow these s= teps to download your filtered logs :
Log viewer
.Format
drop-down.Download logs
.Logs displayed in the table are downloaded. The download is= limited to 200 events at most that match your filters selected.
Create issue
in Post-functionApply filters
The table displays your filtered logs.
The first thing you need to do is look at=
Message
, the last column of the table for the error/warning m=
essage (if any).
Message: The post-functi= on failed to create the Epic because the Epic Name was not provided which i= s mandatory while creating an Epic.
Issue key
filterApply filters
The table displays your filtered logs.
The first thing you need to do is look at=
Message
, the last column of the table for the error/warning m=
essage.
Message: The post-functi= on failed to set Component/s field with a component name "Testing". Cl= icking on > of the log entry and looking at Jir= a REST API call will display information on what value has been pa= ssed to Jira.
Jira REST API call: The Data shows that two components; Backend
and Testing=
were passed to Jira instead of one i.e. "Backend,Te=
sting"
. The comma(',') was considered as a delimiter in the array of=
values rather than a part of the component name. So you need to pass =
the value as JSON object ([=
{"name":"Backend,Testing"}])
selecting the "Treat value=
as JSON"
option in the post-function configuration.
While iterating over linked issues to set=
a field value using Set field value of linked issues post-function, there =
is no way of knowing which issues were impacted. You might then want to set=
the Temporary log level
to DEBUG and trigger=
the transition that has the post-function.
DEBUG
in LevelSet field value of linked issues
in Post-function=
li>
Apply filters
The table displays your filtered logs.
The table now has DEBUG entries indicatin= g the setting of the field on the impacted linked issues.
When using a web= hook, the raw content is sent as a JSON file.
You can use this raw content to construct your own logging messages.
For example, you can derive:
A msgType occurred at time when d=
uring (post-function postFunction=
span>) on issueKey transition transition.transiti=
onName (from status t=
ransition.from_status to status transition.to_status) of workflow
Using the sample data above, this reads:
A license-error occurred at 2022-0=
4-14T14:42:01.408Z when post-fun=
ction-triggered (post-function ClearFieldsFunctio=
n) on MYPROJ-125 transition