Install and configure @eleven-labs/nest-profiler in a NestJS application. Introspects the project, picks an enable strategy (ConditionalModule vs the enabled flag), configures the core, and wires the optional collectors (TypeORM, MikroORM, Mongoose, HTTP, cache, auth, config, GraphQL, validator, commander, RabbitMQ, routes) that match the stack — asking the user to confirm the choices that matter. Use when a user wants to add the profiler to their NestJS app, or enable request / log / exception / query profiling.
Add one optional @eleven-labs/nest-profiler collector package to a NestJS app that already has the core profiler configured. Matches the app's existing enable strategy and placement rules, and applies the collector's wiring gotcha. Use when a project gains a new integration (TypeORM, MikroORM, Mongoose, HTTP client, cache, auth, config, GraphQL, class-validator/zod, nest-commander, RabbitMQ, routes) and the user wants its dedicated profiler panel.
Write a custom @eleven-labs/nest-profiler collector, or a context adapter for a non-HTTP protocol, when no official @eleven-labs/nest-profiler-* package instruments the integration. Use when a user wants a profiler panel for a library/subsystem that has no ready-made collector, or wants to profile a transport (gRPC, WebSockets, a custom queue) the profiler doesn't know yet.
Implement a custom @eleven-labs/nest-profiler storage backend (Redis, a database, S3…) by implementing IProfilerStorageAdapter and wiring it via the `storage` option. Use when the built-in memory / file / sqlite backends don't fit — e.g. profiles must be shared across instances, survive deploys, or live in existing infrastructure.
Harden an existing @eleven-labs/nest-profiler setup for a production (or production-like) environment. Applies the access-control, masking, sampling, retention and persistence checklist so the profiler can run outside local dev without leaking sensitive data. Use when a user wants the profiler enabled in production, on a shared/staging environment, or reachable beyond localhost — or asks how to make an existing setup safe.
Read and act on @eleven-labs/nest-profiler performance tags (slow, n-plus-one, chatty, large-payload, error), tune the thresholds that produce them, and add custom performance rules. Use when a user asks what a profiler tag means, why a request is flagged, how to fix an N+1 / slow / chatty pattern, or how to change or extend the tagging rules.