How LogXray works
Attach the debug log. Add the ER Extract and the PAR of the same object for readable rule text and checks. Nothing leaves your browser.
The log prints Line(S8:22), a section and a line number. LogXray lays those lines over the extract, compares the text as a check, and shows what ran, which branches were taken, table I/O and every business function parameter.
What it can do
Maps log lines to your extract
Each log line, such as
Line(S8:22), is matched to its section and line in the ER Extract, and the text is compared as a check.Shows what ran and which branches were taken
An execution trace laid over the event rules, so you can see the path the run actually followed.
Table I/O
Every table read and write the run performed.
Business function parameters
Every business function call, with every parameter.
Hot spots and loops
Loops are collapsed to one row per statement, with the run count and the total time, so the expensive lines stand out.
A timeline for every line
Click a line to see when it ran, using the log’s own timestamps and line numbers.
Step through a loop
For a loop, step through every pass and see the value on each one.
Flags a mismatch
If a line reads differently in the log than in the extract, it is flagged. The extract may have been exported after a change.
Handles very large logs
Logs over 256 MB are read in chunks, and only the event rule trace lines are kept.
How to use it
Attach the debug log
This is required. Use a
jdedebug.logor a UBE log.Add the extract and the PAR
Add the ER Extract for readable rule text, and the PAR of the same object for an object check. Both should be from the same object as the log.
Click Analyse
LogXray maps each log line to its place in the extract.
Read the results
Check what ran, the branches taken, table I/O and business function parameters. Open Hot spots & loops for the slow statements.
Click a line for detail
See when it ran. For a loop, step through each pass and the value on that pass.
Good to know
- Only the debug log is required. Without the ER Extract, LogXray has less rule text to check against.
- A mismatch flag may mean the extract is out of date, not that the log is wrong.
- Files are processed in your browser. Nothing leaves it.