shuyilink-collector-js v0.1.9

SHUYILINK COLLECTOR JS

shuyilink-collector-js Client-side JavaScript log, exception and tracing library.

• Provide metrics and error collection to backend.
• Lightweight
• Make browser as a start of whole distributed tracing
• Base on skywalking-client-js

Usage

Install

The shuyilink-collector-js runtime library is available at npm.

npm install shuyilink-collector-js --save

Quick Start

User could use register method to load and report data automatically.

import ClientCollector from 'shuyilink-collector-js';

Collector.register({
   service: 'ipc-web',
   pagePath: window.location.ref,
   serviceVersion: 'v1.0.0',
   enableLogs: true,
   consoleLogLevels: ['Info', 'Warning', 'Error'],
   useUploadLogs: true
})

Parameters

The register method supports the following parameters.

Collect Metrics Manually

Use the setPerformance method to report metrics at the moment of page loaded or any other moment meaningful.

1. Set the SDK configuration item autoTracePerf to false to turn off automatic reporting performance metrics and wait for manual triggering of escalation.
2. Call Collector.setPerformance(object) method to report

• Examples

import Collector from 'shuyilink-collector-js';

Collector.setPerformance({
  collector: 'http://127.0.0.1:12800',
  service: 'browser-app',
  serviceVersion: '1.0.0',
  pagePath: location.href,
  useFmp: true
});

Special scene

SPA Page

In spa (single page application) single page application, the page will be refreshed only once. The traditional method only reports PV once after the page loading, but cannot count the PV of each sub-page, and can't make other types of logs aggregate by sub-page.
The SDK provides two processing methods for spa pages:

1. Enable spa automatic parsing
   This method is suitable for most single page application scenarios with URL hash as the route.
   In the initialized configuration item, set enableSPA to true, which will turn on the page's hashchange event listening (trigger re reporting PV), and use URL hash as the page field in other data reporting.
2. Manual reporting
   This method can be used in all single page application scenarios. This method can be used if the first method is invalid.
   The SDK provides a set page method to manually update the page name when data is reported. When this method is called, the page PV will be re reported by default. For details, see setPerformance().

app.on('routeChange', function (next) {
   Collector.setPerformance({
      collector: 'http://127.0.0.1:12800',
      service: 'browser-app',
      serviceVersion: '1.0.0',
      pagePath: location.href,
      useFmp: true
   });
});   

Collect logs manually

It's similar to console.log / console.warn / console.error

Collector.info(`TestLogCollector >> ${count} >> Info`, 'xxxx')

Collector.warn(`TestLogCollector >> ${count} >> Warning`, 'xxxx')

Collector.error(`TestLogCollector >> ${count} >> Error`, 'xxxx')

Tracing range of data requests in the browser

Support tracking these(XMLHttpRequest and Fetch API) two modes of data requests. At the same time, Support tracking libraries and tools that base on XMLHttpRequest and fetch, such as Axios, SuperAgent, OpenApi and so on.

Catching errors in frames

// Vue
Vue.config.errorHandler = (error) => {
   Collector.reportFrameErrors({
      collector: 'http://127.0.0.1:12800',
      service: 'vue-demo',
      pagePath: '/app',
      serviceVersion: 'v1.0.0',
   }, error);
}

According to different pages or modules, add custom tags to spans.

app.on('routeChange', function () {
   Collector.setCustomTags([
      {key: 'key1', value: 'value1'},
      {key: 'key2', value: 'value2'},
   ]);
});

License

Apache 2.0