Link Details

Link 1038243 thumbnail
User 427814 avatar

By jeffreyw
Published: Sep 25 2013 / 01:52

Collecting log events from the browser presents a number of challenges which have hindered the development of a viable solution. There’s no standard means of transmitting log data from the front-end; it’s not like you can pipe it straight to rsyslog. You’re constrained by the same-origin policy. Developing a cross-browser solution means dealing with cross-browser idiosyncrasies. You don’t know in advance where clients will come from, and you don’t have any control over their network topology- so how do you identify individual users? Find out how you can now log client-side JavaScript events straight into your log management tool without needing another app.
  • 11
  • 0
  • 750
  • 755

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Play Framework
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Akka
  2. Design Patterns
  3. OO JS
  4. Cont. Delivery
  5. HTML5 Mobile
  1. Akka
  2. JUnit/EasyMock
  3. Java Performance
  4. REST
  5. Java