This document discusses logging JavaScript errors in Oracle APEX applications. It notes that JavaScript errors currently only display on the client-side and provides no logging. The author then introduces JS-Logger, a tool they developed to log JavaScript errors and related details to a database or via REST. JS-Logger overwrites console logging functions and uses additional libraries to capture stack traces, platform info, workflow, and more to provide richer error information for analysis. The document demonstrates JS-Logger and how it can be implemented in APEX applications.

2. Professional
JavaScript Error-Logging
for Oracle APEX
Kai Donato
Jun 28, 2017 | Kscope17

3. 3
Facts & Figures
Independent Technology House
with Cross-Industry Expertise
Headquarter
Ratingen
(North Rhine – Westphalia)
180
Employees
Founded
1994
Branches
Dortmund, Cologne,
Frankfurt am Main
Top Company
for Trainees &
Students
Privately-
Owned
Corporation
Oracle
Platinum
Partner
28 Mio. Euro
Revenue

4. 4
• Employee at MT AG in Ratingen since January
2014
• Senior Consultant for APEX Development
• DOAG-Initiator - HTML5 and JavaScript
• More than 12 Years expertise in Web-Development
• Systems Integrations Specialist
UNIX-Server and Networkadministration
About me
@_KaiDonat
o
KaiDonato

5. Professional
JavaScript Error-
Logging for Oracle
APEX

8. Usually you used to see all kinds of errors logged into the
database:
• APEX internal errors
• Erroneous PLSQL-Routines
• Any kind of thrown Exceptions
...But what about JavaScript?
Logging with Oracle APEX

9. Doing it the
basic/usual way...
... Let the user describe
what happened in the UI.

10. „Umm ... I just clicked ...
like 3 times on this
button ... and it didn‘t do
what I expected...“
🤷🤷♀️

11. „It simply didn‘t do
anything.“🤷🤷♂️

12. HTML and JavaScript sent
Not happening!
...yet

14. • JavaScript is used in nearly everywhere in APEX
... errors can happen even if you didn‘t write that much JavaScript by
yourself
• JavaScript-Errors are happening on the client-side
... and they stay there if we don‘t do anything about it
• JavaScript might be used just for aesthetic reasons but also for
critical parts of the application
Why logging JavaScript-Errors?

15. JS-Logger

16. JS-Logger
🚀

17. • The console-object contains functions we
can use
• console.log/warn/error will be
thrown automatically - and if you want -
manually
• By overwriting these functions we can
change/extend their behaviour
Console-Object

18. • All JavaScript-Errors/Logs will be inserted into the database or sent via
REST-Call to a remote destination of your choice
• JS-Logger consists of multiple components:
• Dynamic Action Plugin
• Database Objects (optional)
• APEX-Application for analyzing errors (optional)
• Multiple additional libraries were integrated to enrich the error-logs with
further helpful details about the environment
• Stacktrace.js
• Platform.js
JS-Logger

19. • The following metrics will be used to track errors:
• Platform
• Error-message
• Stacktrace
• Workflow (which are the recently visited pages?)
• Current APEX-Page
• Application Version
JS-Logger

20. How to implement JS-Logger?

21. DEMO

25. Kai Donato
Telefon: +49 2102 30961 – 0
kai.donato@mt-ag.com
@_KaiDonato