João Antunes

> Would the error monitoring in Datadog and Bugsnag be more appropriate to catch those failures? The idea would be to leverage the reporting already in place, we wouldn't need...

> which type of production problem would this allow us to detect, that we cannot already detect with the current Datadog metrics sent both by Netlify Build and the buildbot?...

> It seems to me those are different concerns which should be split into different metrics. > Where I was coming from with using the current buildbot metric for build...

Alright, I've taken a look at what we have available in terms of metrics that we could reuse. We can maybe reuse `buildbot.build.error` and `buildbot.build.success` but I guess we would...

AFAIK we already do some error identification in our function bundling which allows us to distinguish between a couple of different error scenarios - https://github.com/netlify/build/blob/main/packages/build/src/plugins_core/functions/error.js#L12-L24. The idea would be to...

> what if we log the debug logs directly to humio without logging it to stdout. Then we could do it for every build. IMO we should take advantage of...

With #2709 merged I'm wondering if we want to take further action here in terms of documenting this or not? Thanks to @ehmicky who pointed out to this discussion -...

Thanks for raising this @marcofugaro. This is definitely related with #612 and #319 and our usage of the `--cache-folder` property 👍 however it isn't particular to your `workspace` settings I...

Hey @denis-sokolov 👋 First of all, thank you very much for putting time and effort into this and the other PRs you've opened and apologies for taking so long to...

Hey @MikeBeas 👋 thank you for reporting this. I believe you're essentially being affected by the way we're currently caching the `node_modules`when using `npm`: https://github.com/netlify/build-image/blob/d84c79427e8f83c1ba17bcdd7b3fe38059376b68/run-build-functions.sh#L149 So this is essentially related...