[Help required] Logging guidance and multi-tenant database connection setup.

[opaque depot]

I searched already asked questions and couldn't find any answers to this.

1. Logging:

I want to log messages from hooks to see if it works as expected. I used the payload.logger.info in one of the hooks but it doesn't work. I am using the multi-tenant template. https://github.com/payloadcms/payload/tree/1.x/examples/multi-tenant

I tried to log in the src/fields/tenant/index.ts in the beforeChange hook like the following payload.logger.info('req.user>>', req.user) but it is not logged to the terminal. What am I missing here?

2. Changing db connection on the fly.

How do I use the payload.db.create or payload.db.drizzle object to change a db connection based on the tenantId. For ex: if TenantId is 1, I want to open a connection to shard-1. The db I am using is postgres. I just want some examples on how to change connections to db on-the-fly programatically.

[opaque hare]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Installation
• Cloud Projects
• MongoDB
• Production Deployment
• Versions

[opaque depot]

Any help is apprreciated

[Help required] Logging guidance and multi-tenant database connection setup.

[manic schooner]

you can use classic console.log to log to the server console

And you can access the payload property inside a hook either by importing payload, or accessing the { req } object from the beforeChange hook props.

example;

export const revalidateDocument: AfterChangeHook = ({
    doc,
    req,
    collection,
    operation,
}) => {
    if (operation === 'update' && doc._status === 'published') {
        const url = formatUrl({ doc });

        const revalidate = async (): Promise<void> => {
            try {
                const res = await fetch(
                    `${process.env.PAYLOAD_PUBLIC_WEBSITE_URL}/api/revalidate?secret=${process.env.REVALIDATION_KEY}&collection=${collection.slug}&slug=${doc.slug}&path=${url}`
                );

                if (res.ok) {
                    req.payload.logger.info(
                        `Successfully hit revalidate route for ${url}`
                    );
                } else {
                    req.payload.logger.error(`Error revalidate path ${url}`);
                }
            } catch (err) {
                req.payload.logger.error(`Error hitting revalidate route for ${url}`);
            }
        };

        revalidate();
    }

    return doc;
};

Keep in mind that hooks are server-side operations, so logging will not show anything in the browser terminal, only your nodejs terminal

[opaque depot]

Hey @manic schooner Thanks for the quick reply! I tried console.log in the hook but it didn't show up in the node terminal. I will give the req.payload option a try. Also, do you have any advice on the second point I have mentioned above?

[manic schooner]

have you tried adding a breakpoint? where are you adding the console.log?

[opaque depot]

On the following after line 29: https://github.com/payloadcms/payload/blob/59fb70077d6ac8870732888233742db3bc5f8038/examples/multi-tenant/src/collections/fields/tenant/index.ts#L29

I didn't try a breakpoint but will give that a try as well.

[manic schooner]

And I'm not sure about changing the current DB on the fly. I would really recommend against doing this as it will result in long times between connections.

You could try using payload.db, that interfaces directly with the underlying database. But I have a feeling that something will break if you attempt to open and close a connection inside of a hook.

Usually in a multi-tenant application, you either share a database but partition data by using some kind of static key to denote the tenant for each record. Or you create seperate databases and seperate applications per tenant, and connect to them when the application first starts

[manic schooner]

Before or after the if condition?

[opaque depot]

Before

[manic schooner]

it sounds more like the hook isn't firing, rather than console.log not working

beforeChange runs when you press the "save" button