Thanks @Nakita, should be all fixed! Thank you for the bug report!
Will implement aggregate filters on the logs dashboard!
Thanks @Nakita, should be all fixed! Thank you for the bug report!
Will implement aggregate filters on the logs dashboard!
You can now view trace latencies in the logs explorer:
@gabriel15, you can now filter aggregates by User or by Thing:
good
I have a question about WU consumption.
We know that WUs are consumed by actions such as Workflows, API calls, etc. These usages seem to be tracked correctly in Buildprint.
My question is related to data reads.
For example:
When a user accesses the app, there is a page load cost, and in addition, there are database search costs to load the data displayed on the page or from other additional searches performed by the app.
Are these data read costs also being counted toward WU consumption?
In other words, do database searches and data loading contribute to the total WUs shown in the dashboard?
Thanks!
Only data fetched in workflows
Data read from pages wonât be included as theyâre not in server logs, but Buildprint can still analyze them - they just wonât be displayed in logs dashboard because logs is for, well, logs
Understood.
Currently, my biggest costs are related to database reads by users (âFetching Dataâ).
It would be extremely helpful to understand which specific data reads are consuming the most WUs, and also which users are responsible for that consumption.
Having that level of visibility would provide great direction for optimization.
Hopefully this is something that could be added in the future.
How to download the documentation, as mentioned here đ Introducing Buildprint | Auto-generated documentation for complex Bubble apps - Is the feature removed ?
Hey @Nakita we donât offer one click Markdown export anymore for a few reasons:
The expectation now is that for any question you wouldâve previously looked at the docs for, just ask your AI. This means itâll always be up to date. Nothing stopping you asking it to generate docs btw.
I might add a documentation library you can structure and generate that gets automatically maintained, but not a priority right now.
You can now share conversations publicly or with team members!
Check out how NQU Secure works:
Can anyone explain how to connect Gemini? I canât figure out how to set up the MCP
I donât think gemini.google.com supports MCP, but Gemini CLI does.
Your best bet is to paste the docs for Gemini and get AI to help you set it up. All youâll need to do is give Gemini the MCP URL and I imagine it can handle the rest.
(And of course, if you donât want to set up MCP, just connect ChatGPT/Claude in Buildprint and chat directly there!)
Thanks, I got the MCP working. Too bad Gemini wonât let us use it directly in the app, itâs been the most helpful AI for me so far
Officially excited about Bubble again. Amazing product ![]()
That was the goal ![]()
If youâre excited about this, then boy will you be excited about what Iâm working on now.
In the onboarding flow, we now include a recommended permissions set for the collaborator, as well as details of how Buildprint can/canât access your data.
Buildprintâs data access permissions are controlled by the level of collaborator access you provide. If you do not want Buildprint to be able to access live data, then you can check the âDev onlyâ checkbox in the collaboration settings. Note that restricting data and logs access to development only will significantly reduce Buildprintâs ability to investigate issues using real data.
Buildprint cannot edit data in your database. Buildprint also cannot see private values in your API Connector or plugin elements - these never leave Bubble and are not saved by Buildprint.
This looks great ![]()
Say more? Migrating bubble or?
Nothing more, just a cool demo ![]()
Just a quick post to say hats off to George and his team - I am blown away by how good Buildprint is. We had an edge case bug report this morning and I decided to try asking buildprint why it might be happening - it went DEEP into my app, incredibly detailed - then suggested what the issue was and how best to fix it. Amazing.
The searchable logs - fantastic.
The ability to have a page recreated (not quite 1:1 but very close) as âcodeâ - WOW.
Anyway - well done George, this is a masterpiece. ![]()
But was it right ![]()
ha! well, because itâs quite an edge case race condition dependant on peoples internet connection speed etc, then itâs hard for me to know âfor sureâ at this moment - but BP gave me some great ideas how to âcatchâ it safety if it does creep in again. So iâm sure it will be perfect ![]()
One question : whatâs the ânone/low/medium/highâ setting for exactly?