Apache SkyWalking Client-side JavaScript exception and tracing library.
- Provide metrics and error collection to SkyWalking backend.
- Lightweight
- Make browser as a start of whole distributed tracing
NOTICE, SkyWalking Client JS 0.8.0 and later versions require SkyWalking v9.
The skywalking-client-js runtime library is available at npm.
npm install skywalking-client-js --save
skywalking-client-js requires SkyWalking 8.2+
User could use register method to load and report data automatically.
import ClientMonitor from 'skywalking-client-js';// Report collected data to `http:// + window.location.host + /browser/perfData` in default
ClientMonitor.register({
# Use core/default/restPort in the OAP server.
# If External Communication Channels are activated, `receiver-sharing-server/default/restPort`,
# ref to https://skywalking.apache.org/docs/main/latest/en/setup/backend/backend-expose/
collector: 'http://127.0.0.1:12800',
service: 'test-ui',
pagePath: '/current/page/name',
serviceVersion: 'v1.0.0',
});The register method supports the following parameters.
| Parameter | Type | Description | Required | Default Value |
|---|---|---|---|---|
| collector | String | In default, the collected data would be reported to current domain(/browser/perfData. Then, typically, we recommend you use a Gateway/proxy to redirect the data to the OAP(resthost:restport). If you set this, the data could be reported to another domain, NOTE the Cross-Origin Resource Sharing (CORS) issuse and solution. |
false | - |
| service | String | project ID. | true | - |
| serviceVersion | String | project verison | true | - |
| pagePath | String | project path | true | - |
| jsErrors | Boolean | Support js errors monitoring | false | true |
| apiErrors | Boolean | Support API errors monitoring | false | true |
| resourceErrors | Boolean | Support resource errors monitoring | false | true |
| useFmp | Boolean | Collect FMP (first meaningful paint) data of the first screen | false | false |
| enableSPA | Boolean | Monitor the page hashchange event and report PV, which is suitable for single page application scenarios. | false | false |
| autoTracePerf | Boolean | Support sending of performance data automatically. | false | true |
| vue | Vue | Support vue2 errors monitoring. Deprecated: This is no longer recommended. Please use the Catching errors in frames scenario instead. | false | undefined |
| traceSDKInternal | Boolean | Support tracing SDK internal RPC. | false | false |
| detailMode | Boolean | Support tracing http method and url as tags in spans. | false | true |
| noTraceOrigins | (string | RegExp)[] | Origin in the noTraceOrigins list will not be traced. |
false | [] |
| traceTimeInterval | Number | Support setting time interval to report segments. | false | 60000 |
| customTags | Array | Custom Tags | false | - |
Use the setPerformance method to report metrics at the moment of page loaded or any other moment meaningful.
- Set the SDK configuration item autoTracePerf to false to turn off automatic reporting performance metrics and wait for manual triggering of escalation.
- Call
ClientMonitor.setPerformance(object)method to report
- Examples
import ClientMonitor from 'skywalking-client-js';
ClientMonitor.setPerformance({
collector: 'http://127.0.0.1:12800',
service: 'browser-app',
serviceVersion: '1.0.0',
pagePath: location.href,
useFmp: true
});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:
- 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. - 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) {
ClientMonitor.setPerformance({
collector: 'http://127.0.0.1:12800',
service: 'browser-app',
serviceVersion: '1.0.0',
pagePath: location.href,
useFmp: true
});
}); 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.
// Angular
import { ErrorHandler } from '@angular/core';
import ClientMonitor from 'skywalking-client-js';
export class AppGlobalErrorhandler implements ErrorHandler {
handleError(error) {
ClientMonitor.reportFrameErrors({
collector: 'http://127.0.0.1:12800',
service: 'angular-demo',
pagePath: '/app',
serviceVersion: 'v1.0.0',
}, error);
}
}
@NgModule({
...
providers: [{provide: ErrorHandler, useClass: AppGlobalErrorhandler}]
})
class AppModule {}// React
class ErrorBoundary extends React.Component {
constructor(props) {
super(props);
this.state = { hasError: false };
}
static getDerivedStateFromError(error) {
// Update state so the next render will show the fallback UI.
return { hasError: true };
}
componentDidCatch(error, errorInfo) {
// You can also log the error to an error reporting service
ClientMonitor.reportFrameErrors({
collector: 'http://127.0.0.1:12800',
service: 'react-demo',
pagePath: '/app',
serviceVersion: 'v1.0.0',
}, error);
}
render() {
if (this.state.hasError) {
// You can render any custom fallback UI
return <h1>Something went wrong.</h1>;
}
return this.props.children;
}
}
<ErrorBoundary>
<MyWidget />
</ErrorBoundary>// Vue
Vue.config.errorHandler = (error) => {
ClientMonitor.reportFrameErrors({
collector: 'http://127.0.0.1:12800',
service: 'vue-demo',
pagePath: '/app',
serviceVersion: 'v1.0.0',
}, error);
}app.on('routeChange', function () {
ClientMonitor.setCustomTags([
{ key: 'key1', value: 'value1' },
{ key: 'key2', value: 'value2' },
]);
});The SkyWalking client-js agent would be deployed and running outside of your datacenter. This means when you introduce this component you should be aware of the security impliciations. There are various kinds of telemetry relative data would be reported to backend separately or through your original HTTP requests.
In order to implement distributed tracing from the browser, an HTTP header with the name sw8 will be added to HTTP requests
according to Cross Process Propagation Headers Protocol v3.
client-js will also report spans and browser telemetry data through Trace Data Protocol v3 and
Browser Protocol.
Because all of this data is reported from an unsecured environment, users should make sure to:
- Not expose OAP server to the internet directly.
- Set up TLS/HTTPs between browser and OAP server.
- Set up authentification(such as TOKEN based) for client-js reporting.
- Validate all fields in the body of the HTTP headers and telemetry data mentioned above to detect and reject malicious data. Without such protections, an attacker could embed executable Javascript code in those fields, causing XSS or even Remote Code Execution (RCE) issues.
Please consult your security team before introducing this feature in your production environment. Don't expose the OAP server's IP/port(s) and URI without a security audit.
Demo project provides instrumented web application with necessary environment, you could just simple use it to see the data SkyWalking collected and how SkyWalking visualizes on the UI. See more information, click here.
- Submit an issue
- Mail list: dev@skywalking.apache.org. Mail to
dev-subscribe@skywalking.apache.org, follow the reply to subscribe the mail list. - Join
#skywalkingchannel at Apache Slack. If the linke is not working, find the latest one at Apache INFRA WIKI.
All committers should follow Release Guide to publish the official release.
Apache 2.0