This page describes debugEnabled in the Server SDK configure method. For the Web SDK, see debugEnabled.
The debugEnabled property turns debug logging on or off for an instance. When debugging is on, the SDK writes messages to your server’s console. These messages include the computed configuration, each method that runs with its options and result, and warnings and errors.
See Enable debug logging for the diagnostic workflow, output location, and runtime scope.
Each message starts with the instance name in square brackets, such as [alloy]. You can change the name with the name property of createInstance.
[alloy] Instance configured. Computed configuration: { ... }
[alloy] Executing getLibraryInfo command. Options: {}
[alloy] getLibraryInfo command resolved. Result: { ... }
Debug messages can include event data and visitor identifiers. Turn on debugging in development environments, and avoid leaving it on in production. The SDK always replaces the client secret in edgeCredentials with [REDACTED] in its logs.
Code example
Set the debugEnabled boolean to true when you call configure. If you omit this property, it defaults to false.
await alloy.configure({
datastreamId: "ebebf826-a01f-4458-8cec-ef61de241c93",
orgId: "ADB3LETTERSANDNUMBERS@AdobeOrg",
edgeCredentials: {
clientId: process.env.ADOBE_CLIENT_ID,
clientSecret: process.env.ADOBE_CLIENT_SECRET,
scopes: process.env.ADOBE_SCOPES.split(",")
},
debugEnabled: process.env.NODE_ENV !== "production"
});
Every forRequest handle uses the same debugEnabled value as the instance that created it. To turn debugging on or off while your server runs, use setDebug.