npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@observertc/observer-js

v0.42.6

Published

Server Side NodeJS Library for processing ObserveRTC Samples

Downloads

545

Readme

Server side component for monitoring WebRTC applications and services

Table of Contents:

Qucik Start

Install it from npm package repository.

npm i @observertc/observer-js

Use it in your server side NodeJS app.

import { createObserver, ClientSample } from "@observertc/observer-js";

const observer = createObserver({
    defaultServiceId: 'my-service-name',
    defaultMediaUnitId: 'my-reporting-component',
});

const observedCall = observer.createObservedCall({
    roomId: 'roomId',
    callId: 'room-session-id',
});

const observedClient = observedCall.createObservedClient({
    clientId: 'client-id',
    mediaUnitId: 'media-unit-id',
});

const clientSample: ClientSample; // Receive your samples, for example, from a WebSocket

observedClient.accept(clientSample);

The above example do as follows:

  1. create an observer to evaluate samples from clients and sfus
  2. create a client source object to accept client samples
  3. add an evaluator process to evaluate ended calls

Get a Summary of a call when it ends


const monitor = observer.createCallSummaryMonitor('summary', (summary) => {
    console.log('Call Summary', summary);
});

How Many Clients are using TURN?

const monitor = observer.createTurnUsageMonitor('turn', (turn) => {
    console.log('TURN', turn);
});

// at any point of time you can get the current state of the turn usage

console.log('Currently ', monitor.clients.size, 'clients are using TURN');

// you can get the incoming and outgoing bytes of the TURN server
console.log(`${YOUR_TURN_SERVER_ADDRESS} usage:`, monitor.getUsage(YOUR_TURN_SERVER_ADDRESS));

Monitor Calls and Clients as they updated

observer.on('newcall', (call) => {
    call.on('update', () => {
        console.log('Call Updated', call.callId);
    });

    call.on('newclient', (client) => {

        client.on('update', () => {
            console.log('Client Updated', client.clientId);

            console.log(`The avaialble incoming bitrate for the client ${client.clientId} is: ${client.availableIncomingBitrate}`)
        });
    })
});

NPM package

https://www.npmjs.com/package/@observertc/observer-js

Schemas

https://github.com/observertc/schemas

License

Apache-2.0