bard-rr / agent-api

This is the api for the agent from the bardrr npm package.

Agent API

Description

This is the api for the Agent from the bardrr npm package. The agent API has four jobs in our infrastructure.

• First, it validates the bardrr Agent using json web tokens.
• Second, it collects the metadata for each session by using the session ID given by the agent to keep track of the time, length, app name, and errors of each session.
• Third, the agent API parses conversion events from regular events and inserts them into the conversion table in the clickhouse database.
• Fourth, it collects all the events from the agent and inserts them into the events table in the clickhouse database.

Required Software

Rabbitmq: Download Here Will be run on port 5672.

Clickhouse: Download Here Will run on port 8123. The schema can be found here Schema

Postgres: Download Here Will run on port 5432. The schema can be found here Schema

Session_Ender: Download Here A Cron job that is responsible for completing sessions and moving them into the clickhouse database.

Setup

Clone the open source reposatory from here. Run the application from the app directory using:

npm run start

The agent api will run on port 3001.

Website

You can read more about our project here.

agent-api's Issues

Enhance metadata handling

Right now, each batch of events that comes into the /record endpoint makes a query to postgres and a query to clickhouse to determine if the events belong to a new session, an active session, or an ended one. Maybe we could enhance this via the use of a key value store like redis so that we don't need to hit the dbs as often?