d2l-telemetry-browser-client

UI Client for sending telemetry from the browser to a telemetry service.

The purpose of this library is to make it easier to construct telemetry events matching the standardized schema (Standard Events) for generating product telemetry as defined in the links below and then to send the events to the Product Telemetry Service.

Base schema for UI Telemetry Events

UI Telemetry Event Schema
Example UI Telemetry Event

UI Performance Event Schema
Example UI Performance Event

UI Problem Event Schema
Example UI Problem Event

As an experiment, there is also a JSON-LD context for defining terms used in TelemetryEvents. This is
an exercise to see if there is value in trying to adopt a common vocabulary. The context is modelled after the IMS Caliper context. Note: JSON-LD is not currently used by any component in the event
processing system, so this is purely documentary at this point.
Experimental Vocabulary

Note: Some properties defined by the telemetry event schema will be set by the backend service when it handles the event.
These include: Version, EventId, Timestamp, TenantId, EventBody.Timestamp, EventBody.Actor.Id, EventBody.TenantUrl, EventBody.Browser.

Usage

$3

Install d2l-telemetry-browser-client via NPM:

``shell
npm install d2l-telemetry-browser-client
`

#### NPM

In NPM, require it normally:

`javascript
const d2lTelemetryBrowserClient = require('d2l-telemetry-browser-client');
`

#### ES6

In ES6, use an import statement:

`javascript
import d2lTelemetryBrowserClient from 'd2l-telemetry-browser-client';
`

The client uses d2l-fetch for making the API requests to the telemetry service.
See the d2l-fetch browser compatibility instructions for additional requirements.

$3

`js

const client = new d2lTelemetryBrowserClient.Client({
endpoint
});

const id = 'http://prd.activityfeed.us-east-1.brightspace.com/api/v1/d2l:orgUnit:6614/article/da1e037d-6a51-4d1a-ba3d-fa62fb5e3591';

// EventBody.Object.Id is currently restricted to simple types which do not include ':' characters
// by current BDP processing. Even though these events are not yet going to BDP, suggestion
// is to either use an internal identifier or encode the URL.
// The URL is included as a new EventBody.Object.Url property.
const eventBody = new d2lTelemetryBrowserClient.EventBody()
.setAction('Created')
.setObject(encodeURIComponent(id), 'Article', id);

const event = new d2lTelemetryBrowserClient.TelemetryEvent()
.setDate(new Date())
.setType('TelemetryEvent')
.setSourceId('activityfeed')
.setBody(eventBody);

client.logUserEvent(event);

`

Development

$3

`shell
npm install
npm run test
`

$3

This repo is configured to use semantic-release. Commits prefixed with fix: and feat: will trigger patch and minor releases when merged to main`.

To learn how to create major releases and release from maintenance branches, refer to the semantic-release GitHub Action documentation.