# Best practices

# Log relevant debugging information

It's recommended to log as much relevant information as possible to the console, as LogRocket includes console output in its session replays.

This applies not only to instrumentation, but also to any frontend code or libraries in use. However, make sure not to log any Personally Identifiable Information (PII).

Here are some examples 👇

# LogRocket verbose mode

import { registerLogRocketInstrumentation } from "@workleap/logrocket";

registerLogRocketInstrumentation("my-app-id", createTelemetryContext, {
    verbose: true
});

# Honeycomb verbose mode

import { registerHoneycombInstrumentation } from "@workleap/honeycomb";

registerHoneycombInstrumentation("sample", "my-app", [/.+/g,], {
    proxy: "https://sample-proxy",
    verbose: true
});

# Mixpanel verbose mode

Initialize Mixpanel with verbose mode:

import { initializeMixpanel } from "@workleap/mixpanel";

initializeMixpanel("wlp", "development", {
    verbose: true
});

# Squide firefly console logger

Initialize Squide firefly with a Console Logger:

import { ConsoleLogger, initializeFirefly } from "@squide/firefly";

const runtime = initializeFirefly({
    loggers: [x => new ConsoleLogger(x)]
});

# Platform widgets verbose mode

Initialize platform widgets with verbose mode:

import { initializeWidgets } from "@workleap-widgets/client/react";

const widgetsRuntime = initializeWidgets("wlp", "development" , {
    verbose: true
});