Shyam Sreevalsan

Completely agree that providing workarounds/exceptions is not the right way forward - for the reasons you listed. Ideally this shouldn't be solved in a way specific to this particular metric...

cc: @cpipilas @ktsaou @hugovalente-pm We've started work on BE (and soon FE) to detect nodes that are disconnected post install and show appropriate information to users, but the work described...

Yes @hugovalente-pm Without this agent fix, the plan is to do: - https://github.com/netdata/cloud-backend/issues/253 on BE to identify such nodes - https://github.com/netdata/cloud-frontend/issues/3594 on FE to notify users about this - https://github.com/netdata/learn/issues/1080...

RDS metrics collected by Amazon CloudWatch are listed [here](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-metrics.html) Amazon CloudWatch instance-level metrics for Amazon RDSThe AWS/RDS namespace in Amazon CloudWatch includes the following instance-level metrics.NoteThe Amazon RDS console might...

@cakrit should we just use the generic ticket and close this one then?

cc: @ilyam8 @vlvkobal @thiagoftsm Creating this final ticket for what we need to get out of PostgreSQL - I know we don't have the capability to do this yet. But...

cc: @ilyam8 @ktsaou @ralphm @cakrit @amalkov @sashwathn

@ktsaou @stelfrag @ilyam8 following on from @ilyam8 comment https://github.com/netdata/netdata/issues/13639#issuecomment-1240433894 > Every hour and every especially 24hrs will not work. > > Every 24hr doesn't work in general. Few notes about...

@cakrit @amalkov @sashwathn might be a good addition to the use-case list. This one is about monitoring the data that the database contains, rather than the database performance. And it...

@ilyam8 yes, this is similar to the telegraf plugin you linked to. Basically, Netdata can become a nice monitoring platform with built in anomaly detection capability for data that can...