Browser-Telemetry
browser-telemetry
module collects client(browser) side errors, logs, metrics(timing & navigation), uncaught exceptions etc and sends back to server for logging & alerting.
Features
- Intercept console.log/error/info/warn on browser
- Intercept Uncaught Exceptions on browser
- Batch update
- Timing & Navigation metrics
- Sampling (Browser side & Server Side)
- Custom Data Provider plugins
Future Enhancements
- Rate Limiting
- Token based API access
- CORS
Usage
Environment
- Minimal Node Version: v8.0.0
Client Side Usage
Add logger.min.js
in header section to load it first, as it hooks console, there by intercepting all JS errors. (see below example)
Minified JS logger.min.js
Example:
Hello World!!
Server Side Usage
let app = ; const path = path; app; app; app; //require Logger let loggerMiddleware = ; //Add Logger Middleware app;
Payload Data
- logs/errors: ALL console logs/errors are intercepted and sent in
logs
field. - Uncaught Exceptions: ALL uncaught exceptions are intercepted and sent in
logs
field asERROR
. - Metrics: Browser load times are captured using timing & navigation API(Only in compatible browsers).
- rc: Redirect Count, number of times page is redirected before hitting current page.
- lt: Load Time, load time of the page.
- ct: Connect Time, time took to connect to server.
- rt: Render Time, time took to render the page.
- navType: Tells you how the page is accessed.
0=Navigate, 1=Reload, 2=History
API
Client Side API
-
#### $logger On load of Javascript file,
$logger
object gets hooked up towindow
object for global access. -
#### $logger.init(object) For initializing logger, call this API. Input:
"url": "api/log" //Relative path"flushInterval": 1000 //1sec,"samplingRate": 10 //10%, Client Side Sampling"isInSampling": true //Flag from Server Side Sampling"sendMetrics": true //Flag to send metrics or not"logLevels": "info" "log" "debug" "error" "warn" //List of enabled console methods -
#### $logger.registerPlugin(pluginName, callback)
- callback(payload) Some times you need to send your own custom data. You can attach custom data or transform data by registering your own plugin. Payload object will be passed, which can be mutated in callback.
On every flush, ALL registered plugins gets called for data transformation.
$logger;
Server Side API
-
#### Middleware #### require('browser-telemetry')(options)
-
options:
- path: Path on which logger should be mounted. This is the end where events from browser are posted.
- log: A callback function which will be invoked on every event from client side.
- request: Holds HTTP request object
- payload: A payload which holds events from browser.
const loggerMiddleware = ;let app = ;...app;
-
-
#### Log Hook As an app developer, you can intercept browser events by hooking to
log
callbacks. Simply pass your custom function while registering middleware as shown below.Browser events are populated in payload param.
app;
File Size
Main motivation for creating this module is to reduce file size. Currently, minified client side JS file size is ~2KB.
Example
See the working example in example
folder.
Running Example Server
node example/server.js //Open Browser pointing to http://localhost:8080 //ALl Logs/Metrics will be dumped on Server side console.
Ackowledgement
This module is created as an inspiration from beaver-logger. Main motivation is to reduce client side JS file size and provide minimal functionality for intercepting logs/metrics/uncaught exceptions on browser side.
Privacy Notice
On running this module/Javascript file on browser, it collects page load metrics, console logs, error logs, unhandled exceptions etc and sends data to backend server for processing.
License
Copyright 2018 eBay Inc.
Use of this source code is governed by an MIT-style license that can be found in the LICENSE file or at https://opensource.org/licenses/MIT.