Hi, I'm from houseofmath.com's infrastructure team, following up on an email from @Graham We are utilizing Growthbook Cloud, Pro and the associated Growthbook Proxy. The proxy is served via Google Cloud Platform, hosted on Cloud Run, which is basically running a proxy docker container that autoscales according to traffic and load. It is also using the Redis cache option, connected to our google managed redis instance. My setup involves a Next.js application hosted on Vercel, integrated with Growthbook through the proxy. The SDK is configured to use the proxy URL, ciphered payload (all 3 options checked), and visual experiments are enabled. The issue I'm encountering is continuous printing of the following in my logs:

| {"level":50,"time":1698754816784,"pid":43,"hostname":"localhost","err":{"type":"SyntaxError","message":"Unexpected token < in JSON at position 0","stack":"SyntaxError: Unexpected token < in JSON at position 0\n    at JSON.parse (<anonymous>)\n    at parseJSONFromBytes (node:internal/deps/undici/undici:6662:19)\n    at successSteps (node:internal/deps/undici/undici:6636:27)\n    at node:internal/deps/undici/undici:1236:60\n    at node:internal/process/task_queues:140:7\n    at AsyncResource.runInAsyncScope (node:async_hooks:203:9)\n    at AsyncResource.runMicrotask (node:internal/process/task_queues:137:8)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"},"msg":"polling error"}

Additionally, on inspecting the website's network tabs, the API calls are successful through the proxy URL. However, all eventstream requests are failing, displaying

"No channel found."

Interestingly, when I use the normal Growthbook URL instead of the proxy, the eventstream works without issues. I'd appreciate any insights or guidance on this matter. I have attached some screenshots. Thank you.

Hi Everyone , Need small help. I have installed growthbook on kubernetes . Deployment is up and running but i can see below error in pod logs. Could you please help.

yarn run v1.22.19
$ wsrun -p 'back-end' -p 'front-end' --no-prefix -c start
$ node dist/server.js
$ next start
ready - started server on 0.0.0.0:3000, url: <http://localhost:3000>
{"level":30,"time":1697208604637,"pid":58,"hostname":"growthbook-74486f46c4-w9htb","msg":"No config.yml file. Using MongoDB instead to store data sources, metrics, and dimensions."}
(node:58) [MONGOOSE] DeprecationWarning: Mongoose: the `strictQuery` option will be switched back to `false` by default in Mongoose 7. Use `mongoose.set('strictQuery', false);` if you want to prepare for this change. Or use `mongoose.set('strictQuery', true);` to suppress this warning.
(Use `node --trace-deprecation ...` to show where the warning was created)
{"level":30,"time":1697208608604,"pid":58,"hostname":"growthbook-74486f46c4-w9htb","msg":"Back-end is running at <http://localhost:3100> in development mode. Press CTRL-C to stop"}
{"level":40,"time":1697208638541,"pid":58,"hostname":"growthbook-74486f46c4-w9htb","err":{"type":"MongooseServerSelectionError","message":"connect ECONNREFUSED 127.0.0.1:27017","stack":"MongooseServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017\n    at NativeConnection.Connection.openUri (/usr/local/src/app/node_modules/mongoose/lib/connection.js:825:32)\n    at /usr/local/src/app/node_modules/mongoose/lib/index.js:414:10\n    at /usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js:41:5\n    at Promise._execute (/usr/local/src/app/node_modules/bluebird/js/release/debuggability.js:384:9)\n    at Promise._resolveFromExecutor (/usr/local/src/app/node_modules/bluebird/js/release/promise.js:518:18)\n    at new Promise (/usr/local/src/app/node_modules/bluebird/js/release/promise.js:103:10)\n    at promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js:40:10)\n    at Mongoose._promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/index.js:1288:10)\n    at Mongoose.connect (/usr/local/src/app/node_modules/mongoose/lib/index.js:413:20)\n    at /usr/local/src/app/packages/back-end/dist/init/mongo.js:34:34\n    at Generator.next (<anonymous>)\n    at /usr/local/src/app/packages/back-end/dist/init/mongo.js:8:71\n    at new Promise (<anonymous>)\n    at __awaiter (/usr/local/src/app/packages/back-end/dist/init/mongo.js:4:12)\n    at exports.default (/usr/local/src/app/packages/back-end/dist/init/mongo.js:21:25)\n    at /usr/local/src/app/packages/back-end/dist/init/index.js:25:43","reason":{"type":"Unknown","servers":{},"stale":false,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"setName":null,"maxElectionId":null,"maxSetVersion":null,"commonWireVersion":0,"logicalSessionTimeoutMinutes":null}},"msg":"Failed to connect to MongoDB. Retrying with field remapping for mongodb v3 to v4"}
{"level":50,"time":1697208668549,"pid":58,"hostname":"growthbook-74486f46c4-w9htb","err":{"type":"MongooseServerSelectionError","message":"connect ECONNREFUSED 127.0.0.1:27017","stack":"MongooseServerSelectionError: connect ECONNREFUSED 127.0.0.1:27017\n    at NativeConnection.Connection.openUri (/usr/local/src/app/node_modules/mongoose/lib/connection.js:825:32)\n    at /usr/local/src/app/node_modules/mongoose/lib/index.js:414:10\n    at /usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js:41:5\n    at Promise._execute (/usr/local/src/app/node_modules/bluebird/js/release/debuggability.js:384:9)\n    at Promise._resolveFromExecutor (/usr/local/src/app/node_modules/bluebird/js/release/promise.js:518:18)\n    at new Promise (/usr/local/src/app/node_modules/bluebird/js/release/promise.js:103:10)\n    at promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/helpers/promiseOrCallback.js:40:10)\n    at Mongoose._promiseOrCallback (/usr/local/src/app/node_modules/mongoose/lib/index.js:1288:10)\n    at Mongoose.connect (/usr/local/src/app/node_modules/mongoose/lib/index.js:413:20)\n    at /usr/local/src/app/packages/back-end/dist/init/mongo.js:50:38\n    at Generator.throw (<anonymous>)\n    at rejected (/usr/local/src/app/packages/back-end/dist/init/mongo.js:6:65)","reason":{"type":"Unknown","servers":{},"stale":false,"compatible":true,"heartbeatFrequencyMS":10000,"localThresholdMS":15,"setName":null,"maxElectionId":null,"maxSetVersion":null,"commonWireVersion":0,"logicalSessionTimeoutMinutes":null}},"msg":"Failed to connect to MongoDB after retrying"}
{"level":50,"time":1697208668550,"pid":58,"hostname":"growthbook-74486f46c4-w9htb","err":{"type":"Error","message":"MongoDB connection error.","stack":"Error: MongoDB connection error.\n    at /usr/local/src/app/packages/back-end/dist/init/mongo.js:54:19\n    at Generator.throw (<anonymous>)\n    at rejected (/usr/local/src/app/packages/back-end/dist/init/mongo.js:6:65)"},"msg":"Failed to initialize application"}
error Command failed with exit code 1.
info Visit <https://yarnpkg.com/en/docs/cli/run> for documentation about this command.
`yarn start` failed with exit code 1

This is my code.

Hi. I've learned that Growthbook could detect an already-used attribute ID so an experiment result will be the same for a particular user. I'm using growthbook in Golang backend and it works well in my local. My current implementation: • Keep a pointer of FeatureMap that will be updated by: ◦ A go routine, regularly fetched the latest feature values ◦ A webhook, register the webhook to Growthbook • On each HTTP request, initiate new growthbook context with attribute ID attached (userID). So, new growthbook instance for each request, using the same feature map. My question: • Where did this attribute ID being cached? How did the growthbook instance know that this or that ID is already assigned with an experiment variation? • If I spawn up 5 replicas of backend service, will the growthbook cached this attribute ID independently in each service? ◦ If so, will this lead to the same user receiving different growthbook experiment result in different service? Thank you in advance!

I am looking to create some time bound metrics - let’s say Day 7 conversion for argument’s sake. Is there a way to exclude users from a calculation (both numerator and denominator) if the user, for example, registered fewer than 7 days ago? My first thought was to create a calculation that could be used as a denominator, which returned the

user_id

and the registration timestamp, with a where clause that required the date diff between registration timestamp and current timestamp to be greater than 7 days. I need to return the registration timestamp so that the conversion window for the conversion metric works properly, but by definition the registration timestamp is before the user is bucketed in the experiment, so is not counted in the experiment calculation. Would very much appreciate help here - there are lots of metrics that we need to write in this way to align with our other reporting.

Hello, I wanted to ask a question about conversion windows and ratio metrics meaning data from outside of the experiment is including in calculations for the experiment. If I have a ratio metric where the denominator can occur substantially (in time) before the numerator, from what I can see I need to include a conversion window value. For my use case, this can be the length of the experiment, so might be high 10s of hours up to anything around 100 or 200. Setting a conversion window to 100 for example means that the endDate values in the generated query end up getting timeshifted by +100 hours, so if I’m doing retrospective analysis (or I have phases set up), I end up including data from outside of the time period of interest. I’m aware of the startDate and endDate jinja keywords that I can include in the definition of the metrics, but these end up getting affected by the conversion delay/window values too. The only workaround at the moment seems to be hardcoding date filters into the queries retrieving the data for the metrics which isn’t viable for anything other than playing around to work out how Growthbook functions. Am I missing something or am I doing something incorrect in my setup? Thanks in advance.

If we use custom data source, for example mysql, what is the best pratice database schema do we need to prepare? What table and field need to define? Is there any document mention about that?

Hey! First time thinking about using namespaces and I want to make sure I'm setting this up correctly. We have an experiment A running for some users newer than a certain timestamp. I used the

Percent of traffic included in this experiment

to narrow it down to only 50% of eligible users go into the test. Now i want to make this mutually exclusive with something else at a 50-50 split. I set up a namespace and gave am thinking of giving experiment A 50% of the namespace and then setting

Percent of traffic included in this experiment

to 100%. Would this yield the same result? Will I inadvertently change which bin people are going to by switching to a namespace? Thanks!

Hey everyone, I recently completed a C# port of the GrowthBook SDK. I saw the growthbook-dotnet project, but wasn't able to determine the status of it, so I went ahead and wrote my own. The lib is available on NuGet and GitHub. If nobody has contributed a C# lib to the main project already, I'd be glad to do so.

Anyone succeeded with deploying growthbook on k8s ? Or on server less like cloud run?