🚀 traxx

A minimal, production-ready route analytics toolkit for Express.js.

Tracks every request — latency, status codes, request metadata, and errors — and stores it asynchronously in MongoDB using BullMQ + Redis.

Built for SaaS platforms, internal tools, and teams who care about visibility without bloat.

📦 Features

• ✅ Tracks route method, status code, latency, timestamp
• 📊 Captures request details: body, params, query
• 🧵 Captures error stack + message (if request fails)
• ⚙️ Asynchronous writes via BullMQ (Redis)
• 🧱 MongoDB model access for custom queries
• 🔔 Notifications via Teams, Slack, and Google Chat for specific status codes with detailed error information

🧪 Installation

npm install traxx

⚙️ Quick Start

const express = require("express");
const Traxx = require("traxx");

const app = express();

const traxx = new Traxx({
  mongoUri: process.env.MONGO_URI,
  redisUri: process.env.REDIS_URI,
  logIPAddress: true, //false by default
  notifications: {
    statusCodes: [404, 500], // or { min: 400, max: 599 } for all error codes
    channels: [
      {
        type: 'teams',
        options: {
          webhookUrl: process.env.TEAMS_WEBHOOK_URL
        }
      },
      {
        type: 'slack',
        options: {
          webhookUrl: process.env.SLACK_WEBHOOK_URL
        }
      }
    ]
  }
});

// Enable tracking middleware without any custom fields
app.use(traxx.middleware());

// if needed to add any custom fields for tracking purpose, like the tenantId
app.use((req, res, next) => traxx.middleware({tenantId: req.body.tenantId})(req, res, next))

// Example route
app.get("/shop/:id", (req, res) => {
  res.json({ status: true, shop: req.params.id });
});

//Start the server and initialize the traxx
const port = process.env.PORT || 8080;
const server = app.listen(port, async () => {
  await traxx.init(); // Connect to Mongo + Redis
  console.log(`Listening on port ${port}...`);
});

🟦 TypeScript Usage

Traxx ships with built‑in type declarations. No extra typings are required.

Install

npm install traxx

Import

// Option A: with esModuleInterop (recommended)
import Traxx from "traxx";

// Option B: without esModuleInterop
// import Traxx = require("traxx");

Example (Express + TS)

import express from "express";
import Traxx from "traxx";

const app = express();

const traxx = new Traxx({
  mongoUri: process.env.MONGO_URI as string,
  redisUri: process.env.REDIS_URI as string,
  logIPAddress: true,
  notifications: {
    statusCodes: { min: 400, max: 599 },
    channels: [
      {
        type: "teams",
        options: { webhookUrl: process.env.TEAMS_WEBHOOK_URL as string },
      },
    ],
  },
});

// Enable tracking middleware
app.use(traxx.middleware());

// Add custom fields (e.g., tenantId)
app.use((req, res, next) =>
  traxx.middleware({ tenantId: (req as any).tenantId })(req, res, next)
);

app.get("/shop/:id", (req, res) => {
  res.json({ status: true, shop: req.params.id });
});

const port = Number(process.env.PORT) || 8080;
app.listen(port, async () => {
  await traxx.init();
  console.log(`Listening on port ${port}...`);
});

Types

• Options type: Traxx.TraxxOptions
• Mongo model: Model<Traxx.TraxxLog>

const Log = traxx.model();
const recent = await Log.find().sort({ timestamp: -1 }).limit(50);

Minimal tsconfig.json

{
  "compilerOptions": {
    "target": "ES2020",
    "module": "CommonJS",
    "esModuleInterop": true,
    "skipLibCheck": true
  }
}

🔍 What Gets Tracked

Each request is stored as its own document — no pre-aggregation, full raw logs for full custom analytics.

🧱 Access the MongoDB Model

Need to build your own dashboard or metrics?

const Log = traxx.model();//get the model instance
const recent = await Log.find().sort({ timestamp: -1 }).limit(50);

🔔 Notification Configuration

Traxx can send notifications to Teams, Slack, and Google Chat when specific status codes are encountered.

Status Code Configuration

You can specify which status codes should trigger notifications in several ways:

// Specific status codes as an array
notifications: {
  statusCodes: [404, 500, 503],
  // ...
}

// Range of status codes
notifications: {
  statusCodes: { min: 400, max: 599 }, // All 4xx and 5xx errors
  // ...
}

Channel Configuration

Configure one or more notification channels:

notifications: {
  statusCodes: [500],
  channels: [
    {
      type: 'teams',
      options: {
        webhookUrl: 'https://outlook.office.com/webhook/...'
      }
    },
    {
      type: 'slack',
      options: {
        webhookUrl: 'https://hooks.slack.com/services/...'
      }
    },
    {
      type: 'googleChat',
      options: {
        webhookUrl: 'https://chat.googleapis.com/v1/spaces/...'
      }
    }
  ]
}

Comprehensive Notification Data

Notifications include all data that is tracked in the database:

• Basic Request Info: Method, route, status code, latency, timestamp
• Request Data: Request body, parameters, query string
• Response Data: Response body
• Custom Fields: Any custom fields passed to the middleware
• IP Address: Client IP address (if logIPAddress is enabled)
• Error Information: Error message and stack trace

This comprehensive data helps you quickly identify and diagnose issues when they occur, with all the context you need to reproduce and fix problems.

Error Information in Notifications

Notifications automatically include detailed error information when available:

• Error Message: The error message is displayed prominently in the notification
• Error Stack: For debugging purposes, the full stack trace is included when available
• Automatic Error Detection: Even for status codes without explicit errors, Traxx generates appropriate error messages

This helps you quickly identify and diagnose issues when they occur.

🧠 Why Traxx?

• Built for modern Express apps
• Tracks everything you need, nothing you don't
• Async, performant, and ready for production

🚀 Nginx Configuration (For Reverse Proxy Setup, if logIPAddress is set to true)

If you're running Traxx behind an Nginx reverse proxy, make sure to update your Nginx configuration to forward the real client IP properly. This ensures that Traxx can log the original client IP instead of the reverse proxy IP (127.0.0.1).

Nginx Configuration

In your Nginx configuration (typically found in /etc/nginx/nginx.conf or /etc/nginx/sites-available/default), make sure to include the following:

server {
    listen 80;

    # Forward the real client IP to the Express app
    location / {
        proxy_set_header X-Forwarded-For $remote_addr;  # Pass the original client IP
        proxy_set_header X-Real-IP $remote_addr;        # Pass the original client IP
        proxy_set_header Host $host;                    # Preserve the original Host header
        proxy_pass http://your_backend_upstream;         # Replace with your Express app URL
    }
}

With this setup:

• Traxx will correctly capture the real client IP via the X-Forwarded-For header.
• If you're using multiple proxies, this setup will always capture the first IP in the chain (the client's original IP).

👨‍💻 Author

Made with 💻 by boopathi-srb

📄 License

CC-BY-NC-4.0