Skip to main content

​
Installation

pnpm add @usesentinel/elysia

​
Basic usage

Add the Sentinel middleware to your Elysia application after CORS:
app.ts
import { Elysia } from "elysia";
import { cors } from "@elysiajs/cors";
import { sentinel } from "@usesentinel/elysia";

const app = new Elysia()
  .use(cors())
  .use(sentinel()) // That's it!
  .get("/", () => "Hello World")
  .listen(3000);
The middleware automatically tracks all incoming requests, captures request/response metadata, and sends events to Sentinel with minimal performance impact.

​
Configuration

The SDK automatically reads configuration from environment variables. You can also pass options directly to the middleware.

​
Configuration options

You can pass configuration options directly when initializing the middleware:
app.ts
app.use(
  sentinel({
    apiKey: "sk_...", // Optional if SENTINEL_API_KEY is set
    batchSize: 50, // Optional, default 50
    flushInterval: 5000, // Optional, default 5000ms
    excludePaths: ["/health", "/metrics"], // Optional
  })
);
​
apiKey
string
Your Sentinel API key. Overrides the SENTINEL_API_KEY environment variable if provided.
​
batchSize
integer
default:"50"
Maximum number of events to batch before sending to the Sentinel API.
​
flushInterval
integer
default:"5000"
Time in milliseconds to wait before sending a batch of events, even if the batch size hasn’t been reached.
​
excludePaths
string[]
Array of path patterns to exclude from tracking. If you specify /v1/projects, it will exclude all paths starting with that prefix (e.g., /v1/projects, /v1/projects/123, /v1/projects/123/tasks).

​
Tracking steps

Track sub-operations within a request to monitor database queries, external API calls, and other operations.
app.ts
import { registerStep, type SentinelContext } from "@usesentinel/elysia";

app.get("/users", async ({ ...context }) => {
  const sentinel = (context as { sentinel?: SentinelContext }).sentinel;

  // Track a database query
  let endDbStep: (() => void) | undefined;
  if (sentinel) {
    endDbStep = registerStep(sentinel.requestId, "db_query", {
      table: "users",
      operation: "SELECT",
    });
  }
  const users = await db.query("SELECT * FROM users");
  endDbStep?.(); // Step completes here

  // Track an external API call
  let endApiStep: (() => void) | undefined;
  if (sentinel) {
    endApiStep = registerStep(sentinel.requestId, "external_api_call", {
      service: "payment_gateway",
    });
  }
  const payment = await fetch("https://api.payment.com/charge", {
    method: "POST",
    body: JSON.stringify({ amount: 100 }),
  });
  endApiStep?.();

  return users;
});
Steps are automatically included in the event sent to Sentinel, allowing you to see which parts of your request took the longest. This helps identify performance bottlenecks.

​
Setting user context

Identify users making requests by setting the userId for tracking user behavior:
app.ts
import { setUserId, type SentinelContext } from "@usesentinel/elysia";

app.get("/users", async ({ ...context }) => {
  // Get user from your auth system
  const user = await getCurrentUser();

  // Identify the user making the request
  const sentinel = (context as { sentinel?: SentinelContext }).sentinel;
  if (sentinel) {
    setUserId(sentinel.requestId, user.id);
  }

  return users;
});
The userId is automatically included in the event sent to Sentinel, enabling user-specific analytics and tracking.

​
How it works

The middleware automatically handles the following:
  • Request tracking: Captures all incoming requests and their metadata
  • Response capture: Records response status codes and timing information
  • Event batching: Groups events together to minimize API calls
  • Automatic retries: Handles failures gracefully with exponential backoff (up to 3 retries by default)
  • Performance optimization: Non-blocking event sending ensures minimal impact on your application
Events are batched and sent automatically in the background. Failed requests are automatically retried with exponential backoff, so your application flow is never interrupted.
Ensure your SENTINEL_API_KEY environment variable is set in production. Without it, events will not be sent to Sentinel.