Versions Compared

Old Version 4

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

compared with

New Version 5

changes.mady.by.user Kirstin Seidel-Gebert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space WBRIDGE and version 7.7.0

...

LogTechnical NameDescription
Standard LogbridgeserverContains logging information logged by the Bridge process that is running the selected xUML service.
Transaction LogtransactionContains transactional logging information logged by the Bridge process that is running the selected xUML service. The logged information is usable for performance measurements or statistical evaluations (how often has the transaction been called, in which context, etc.).
Start LogstartContains information about the selected xUML service, environment variables, and errors logged by the Bridge process at startup.
Stop LogstopContains information about the selected xUML service and errors logged by the Bridge process when stopping it.
A stop log is available, if the service could not be stopped regularly but if errors occurred upon stopping, or if the service had to be killed.
Custom Logs<your name>

The Bridge can also display custom logfiles. To be able to access this custom logfiles via the Bridge, they must meet certain conditions that are explained in detail further below.

Image Added

Custom Logs

Multiexcerpt
MultiExcerptNamecustom_logs

The Bridge can also display custom logfiles. To be able to access this custom logfiles via the Bridge, they must meet the following conditions:

...

ConditionDescription
Save LocationCustom log files of a service must be saved to the /logs folder of the service data directory.

...

Naming Scheme

Names of custom log files must conform to the following naming

...

scheme:

<custom name part>.logfor logs that do not rotate
<custom name part>_yyyy-mm-dd.logfor logs that rotate per day
<custom name part>_yyyy-mm-dd-hh.logfor logs that rotate per hour

The custom name part of the logfile must not contain underscores and must not be one of the reserved log types mentioned

...

above.

Log File Content Format

The log files can be in text or in JSON (Bridge 7.7.0) format. If the log files are in JSON format, they must contain the following properties which will be displayed:

  • timestamp: Timestamp
  • message: Log message
Info
iconfalse

Log files in JSON format can be filtered in the same way as text log files. See Filtering the Log Entries below.

...


Filtering the Log Entries

...

Filter ElementDescriptionDefault
Search for
Multiexcerpt include
MultiExcerptNamels_search_for
PageWithExcerptINTERNAL:_bridge_excerpts
empty
in type

Select the type of logfile you want to display: bridgeserver, start, stop, transaction, custom log types. See top of this page for more information on the log types.

The log types types in this list are displayed in this list in alphabetical order, and the first log type of this list will be the default. So, if you added add a custom log named aa.log, this log will be displayed on going to the Logging page.		first available log type
with log levelSelect the log level of the log entries you want to inspect. Refer to Log Levels of an xUML Service for more information on log levels and what information they contain.
This filter is available for the xUML service standard log (bridgeserver) and the transaction log.		Debug
from
Multiexcerpt include
MultiExcerptNamedate_search
PageWithExcerptINTERNAL:_bridge_excerpts

Pressing Enter in these fields triggers the search.
To enter the dates, you can use a date picker next to the input fields: . Refer to section The Date Picker for more information on this.

Info
iconfalse

The timestamp must follow one of the following patterns if you want to use this filtering feature for your custom logs:

  • YYYY-MM-DD HH:MI:SS or [YYYY-MM-DD HH:MI:SS
  • HH:MI:SS or [HH:MI:SS

It is allowed to put the timestamp in square brackets.

actual timestamp - 10 min
toempty

...

Filter ElementDescriptionDefault
timestampEnter a timestamp you want to analyze in more detail. As per default, this is prepopulated with the timestamp of the selected log entry.Timestamp of the selected log entry.
time focus

To analyze what happened around the selected time stamp, you can choose between:

  • What happened before the selected timestamp?
  • What happened after the selected timestamp?
  • What happened around the selected timestamp?
What happened before
time frameSet a time frame in relation to your selected focus: What happened within the specified time frame before/after/around the selected timestamp?1 second
clear search termRemove a specified search term from the search filter for this refinement to get more search results.false
clear log levelRemove a specified log level from the search filter for this refinement to get more search results.false

Custom Logs

The Bridge can also display custom logfiles. If a service produces log files that

...