my logs using pino are not showing in better auth

i have this for example

const logger = createChildLogger({ module: 'auth' });

onSubscriptionComplete: async ({ subscription, plan }) => {
const foundUser = await getUserByReferenceId(
subscription.referenceId
);
if (foundUser) {
// Set credits based on plan (basic: 150, pro: 300)
try {
const credits = creditService.getCreditsForPlan(plan.name);
await creditService.setCredits(
subscription.referenceId,
credits
);
logger.info(
{
userId: subscription.referenceId,
plan: plan.name,
credits,
},
'Credits set on subscription complete'
);
} catch (error) {
logger.error(
{ err: error, userId: subscription.referenceId },
'Failed to set credits on subscription complete'
);
}

await emailService.sendSubscriptionWelcomeEmail(
foundUser.email,
plan.name,
foundUser.name
);
}
},

every time i make a subscription with stripe i cant see the logs using pino

FabrícioOP•11/24/25, 8:20 PM

@Better Auth why my logs are not showing in better auth?
i am using the stripe plugin and pino js logger

Better Auth•11/24/25, 8:21 PM

Hey there! Thanks for reaching out. Better Auth uses an internal logging mechanism that by default prints errors and other important events, so if you're not seeing logs when using the Stripe plugin with your pino logger, here are a few things to check:

Ensure that your Better Auth configuration is passing your pino logger instance correctly. Verify that your auth configuration includes the proper logger setup and that the log level set in pino matches the levels emitted by Better Auth.
Double-check your environment variables and any Better Auth-specific logger options. Sometimes logs might not appear if the log level is set too high or if the logger isn’t fully integrated with the Better Auth adapter.
It’s also a good idea to see if other parts of Better Auth are logging as expected. If logging works for other modules but not for the Stripe plugin, there might be a configuration nuance there. There’s no explicit documentation about pino integration in our official docs [1], so it could be related to how the logger is wired up in your project.

Could you let me know if your pino logger is logging events from other parts of your app, or share a snippet of your auth configuration? That might help pinpoint the issue further.

Sources:
[1] Stripe | Better Auth

— Better Auth is powered by https://clarm.com

Stripe | Better Auth

Stripe plugin for Better Auth to manage subscriptions and payments.

FabrícioOP•11/24/25, 8:22 PM

@Better Auth yes, the pino logger show the log info of others parts, but if i need to log something inside better auth, nothing appear in the logs

Better Auth•11/24/25, 8:22 PM

It sounds like the issue might be related to the logger configuration in your Better Auth setup. By default, Better Auth uses its own logger settings—which include a log level (for example, “error”) that filters out lower-level logs like “info”. If you’re using Pino externally and you’re seeing other logs but nothing from within Better Auth, you may need to adjust the logger options in your Better Auth configuration. For instance, setting the logger’s level to "info" and ensuring it’s not disabled could help display the logs you're expecting [2], [3].

Could you share how you’ve configured the Better Auth logger in your code, or let me know what specific messages you expect to see?

Sources:
[2] Options | Better Auth
[3] fix: logger respects BetterAuthOptionsBetterAuthOptions

— Better Auth is powered by https://clarm.com

GitHub

Build software better, together

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

Options | Better Auth

Better Auth configuration options reference.

GitHub

fix: logger respects `BetterAuthOptions` by LightTab2 · Pull Reque...

There are some places where one needs to use a module-defined logger; however, in some of them, it&#39;s still possible to take note of the logger options from {BetterAuthOptions}.
Honestly, I ...

FabrícioOP•11/24/25, 8:28 PM

@Better Auth what config do i need to include in the better auth config to see my logs?

Better Auth•11/24/25, 8:29 PM

To see logs in Better Auth, you need to include a logger option in your configuration with settings that enable and control the log output. For example, you can configure it like this:

import { betterAuth } from "better-auth";

export const auth = betterAuth({
  logger: {
    disabled: false,               // Ensure logging is enabled (default is false)
    level: "info",                 // Set the minimum log level (e.g., "info", "debug", "error")
    disableColors: false,          // (Optional) Enables colored log output if your terminal supports it
    log: (level, message, ...args) => {
      // Custom logging function implementation
      console.log(`[${level}] ${message}`, ...args);
    }
  }
});

import { betterAuth } from "better-auth";

export const auth = betterAuth({
  logger: {
    disabled: false,               // Ensure logging is enabled (default is false)
    level: "info",                 // Set the minimum log level (e.g., "info", "debug", "error")
    disableColors: false,          // (Optional) Enables colored log output if your terminal supports it
    log: (level, message, ...args) => {
      // Custom logging function implementation
      console.log(`[${level}] ${message}`, ...args);
    }
  }
});

This configuration ensures that logs at or above the specified level (here "info") will be output. The custom loglog function allows you to control how logs are formatted and where they are sent [1].

Can you let me know if you need help with any custom logging hooks or further adjustments to your log setup?

Sources:
[1] Options | Better Auth

— Better Auth is powered by https://clarm.com

Options | Better Auth

Better Auth configuration options reference.

FabrícioOP•11/24/25, 8:30 PM

@Better Auth and to see the logs here?

onSubscriptionComplete: async ({ subscription, plan }) => {
const foundUser = await getUserByReferenceId(
subscription.referenceId
);
if (foundUser) {
// Set credits based on plan (basic: 150, pro: 300)
try {
const credits = creditService.getCreditsForPlan(plan.name);
await creditService.setCredits(
subscription.referenceId,
credits
);
logger.info(
{
userId: subscription.referenceId,
plan: plan.name,
credits,
},
'Credits set on subscription complete'
);
} catch (error) {
logger.error(
{ err: error, userId: subscription.referenceId },
'Failed to set credits on subscription complete'
);
}

await emailService.sendSubscriptionWelcomeEmail(
foundUser.email,
plan.name,
foundUser.name
);
}
},

Better Auth•11/24/25, 8:30 PM

It looks like your code is structured so that when a subscription is completed, the event handler logs an info message via logger.info (with details such as the user’s referenceId, plan, and assigned credits) and logs an error via logger.error if setting credits fails. This means that if everything is set up correctly in your environment, you should see these log messages in the output of your logger (for example, in your server console or your logging service configuration) [1].

If you’re not seeing the logs, here are a few things to check:

Make sure that your logger is configured to output info-level logs (or lower), so that these messages aren’t filtered out.
Verify that your deployment environment isn’t redirecting or suppressing these logs.
Confirm that there are no issues with how the logger is integrated with your application.

Is your logger configured to write to the expected output (e.g., console or a log file), or are you using an external logging service?

Sources:
[1] Upgrading / switching plans sets status to past_duepast_due

— Better Auth is powered by https://clarm.com

GitHub

better-auth/better-auth

The most comprehensive authentication framework for TypeScript - better-auth/better-auth

GitHub

Upgrading / switching plans sets status to `past_due` · Issue #356...

Is this suited for github? Yes, this is suited for github To Reproduce Create a stripe config with 2 plans. Subscribe to one plan. Upgrade to the other plan. Current vs. Expected behavior It works ...

my logs using pino are not showing in better auth

Similar Threads

Similar Threads

Similar Threads