Custom logging

By default, SDKs output info and error logs to the console.

You can provide a custom logging callback to capture and forward logs elsewhere, e.g. to your monitoring infrastructure, by setting localLogger in your createSource options:

Server

src/lib/getHypertune.ts

import { createSource } from "../generated/hypertune";

const hypertuneSource = createSource({
  token: process.env.HYPERTUNE_TOKEN!,
  localLogger: (level, message, metadata) => {
    console.log(level, message, metadata);
  },
});

export default async function getHypertune() {
  // Get flag updates in serverless environments
  // await hypertuneSource.initIfNeeded();

  return hypertuneSource.root({
    args: {
      context: {
        environment:
          process.env.NODE_ENV === "development"
            ? "development"
            : "production",
        user: { id: "1", name: "Test", email: "[e-mail]" },
      },
    },
  });
}

Browser

src/components/AppHypertuneProvider.tsx

import { HypertuneProvider } from "../generated/hypertune.react";

export default function AppHypertuneProvider({
  children,
}: {
  children: React.ReactNode;
}) {
  return (
    <HypertuneProvider
      createSourceOptions={{
        token: import.meta.env.VITE_HYPERTUNE_TOKEN!,
        localLogger: (level, message, metadata) => {
          console.log(level, message, metadata);
        },
      }}
      rootArgs={{
        context: {
          environment:
            process.env.NODE_ENV === "development"
              ? "development"
              : "production",
          user: { id: "1", name: "Test", email: "[e-mail]" },
        },
      }}
    >
      {children}
    </HypertuneProvider>
  );
}

---

localLogger?: (
  level: LogLevel,
  message: string,
  metadata: object
) => void;

enum LogLevel {
  Debug = 'Debug',
  Error = 'Error',
  Info = 'Info',
  Warn = 'Warn'
}