Austin S. Hemmelgarn

Looks like there’s a build failure in the static build check related to this (see https://github.com/netdata/netdata/pull/11372/checks?check_run_id=3280903212). You can test that locally by running `packaging/makeself/build-x86_64-static.sh` from the root of a clean...

> Looks like some jobs are still queued. Also, failed jobs are for external reasons. @Ferroin could you please check this? The Fedora AWS Kinesis build can be ignored, as...

@raven428 Any chance you could rebase this onto the latest master? I suspect the CI failures we were seeing will simply evaporate, at which point it should be relatively quick...

Most likely not related to https://github.com/netdata/netdata/issues/13178 (that particular issue should not be affecting anything but configuration, and it’s an external issue in webmin). Regarding updates, stable versions, and such: -...

Yep, Ubuntu 22.04 should be no problem at all. It sounds like you may have to manually update the repos though (unfortunately, unlike on RPM systems, there’s no way to...

Quick update based on internal discussion: My initial comment that this was probably unrelated to https://github.com/netdata/netdata/issues/13178 may be wrong. If non-default settings for the dbengine (or history if you’re using...

I concur with @ktsaou here, both on the point of this being part of the health management info, and on needing it to be more than simply a boolean flag,...

@ralphm Indeed, that’s almost certainly a better approach in terms of scalability. I still think any configuration overrides should probably be in the health section on the client side (or...

> sure we could clean up nodes known to be ephemeral earlier, but it also depends on what the topology looks like. I.e. if there's a parent node with long...

> As I was thinking about this now. Should this be .dotfile (like in case of .do_not_track) so that it could easily be set by installer/claim script etc.? Probably as...