Hello Everyone! Happy New Year! :champagne: We have just released version 2.7. Here are some of the ...
g

Graham

over 1 year ago
Hello Everyone! Happy New Year! 🍾 We have just released version 2.7. Here are some of the new features we've added. • Sticky Bucketing for JS SDK users. Sticky Bucketing allows you to remember the first variation a user sees, so their experience will remain consistent, even if something changes that would otherwise re-assign them. This is an opt-in feature. (Read the docs) • Reusable Targeting Conditions. Just like the saved groups, you can now save targeting conditions to make targeting new features to previously targeted users easier. (docs) • Huge improvements to the fact table queries. For our enterprise customers, we've greatly improved the efficiency of queries when using fact tables. (blog post about it) • All experiment reports now have a health tab. You can see SRM warnings and other information about the health of your experiment. (docs) • Safely Update Live Experiments. Changing a live experiment mid-flight is much more complicated than many people realize. This feature guides you some of the issues and helps you make the right decision for your experiment. Read the blog post about this featureNew Best Practices Guide. We've added a new section to our documentation site which contains guides on experimentation in general and chapters specifically on how to get the most out of GrowthBook. Link • Contextual AI bot for helping you answer your questions, trained on all our documentation and systems. And lots of other bug fixes and improvements, Okta SCIM improvements, and more. You can read about it on our blog post: https://medium.com/growth-book/new-growthbook-version-2-7-ea4d0e8c2ed6 or on our GitHub: https://github.com/growthbook/growthbook/releases
🥂 7
👍 3
🙌 13
Hello, I'm setuping growthbook as self hosted version on kubernetes. I create one deployment for ui ...
g

Geoffrey Laurent

over 1 year ago
Hello, I'm setuping growthbook as self hosted version on kubernetes. I create one deployment for ui and api with only 1 replica and an other deployment for proxy with 3 replica (for a stress test) I have few questions • api use to crash. ui app work but without api I just have "fail to fetch", here the logs
yarn run v1.22.19
$ wsrun -p 'back-end' -p 'front-end' --no-prefix -c start
$ next start
$ node dist/server.js
ready - started server on 0.0.0.0:3000, url: <http://localhost:3000>
{"level":30,"time":1702482550777,"pid":60,"hostname":"deployment-ui-9c56d45c7-wkhl6","msg":"No config.yml file. Using MongoDB instead to store data sources, metrics, and dimensions."}
(node:60) [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":1702482551567,"pid":60,"hostname":"deployment-ui-9c56d45c7-wkhl6","msg":"Back-end is running at <http://localhost:3100> in development mode. Press CTRL-C to stop"}
{"level":30,"time":1702483922168,"pid":60,"hostname":"deployment-ui-9c56d45c7-wkhl6","msg":"Start Refreshing Results for experiment exp_8kpn21nlq3kyzxc"}
Killed
error Command failed with exit code 137.
info Visit <https://yarnpkg.com/en/docs/cli/run> for documentation about this command.
`yarn start` failed with exit code 137
• I saw in doc to set PROXY_HOST_PUBLIC=https://growthbook-proxy.example.com I think it's for invalid cach, if we have multi proxy clusters (1 by kub cluster) can I add multilple URL ? • in proxy log I have this : "msg":"connection polling: no connections found" what is it about ? thanks Geoffrey