You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're running our postgres instances on Aiven where the master and read replica pairs share the same syslog integration.
Because at the moment, pganalyze's syslog server can't distinguish logs that come from different sources, we don't have visibility into the performance of our replicas.
There's a comment in the code mentioning a TODO for disambiguating logs based on different sources:
Any idea if you plan to prioritize this anytime soon? We have multiple clusters we are managing, and without a way to separate different servers and/or Clusters, the logs feature is essentially useless.
We're running our postgres instances on Aiven where the master and read replica pairs share the same syslog integration.
Because at the moment, pganalyze's syslog server can't distinguish logs that come from different sources, we don't have visibility into the performance of our replicas.
There's a comment in the code mentioning a TODO for disambiguating logs based on different sources:
collector/input/system/selfhosted/syslog_log_receiver.go
Lines 70 to 71 in 290466d
We're very fond of pganalyze and would love to get the ability to have visibility into the performance of both our masters and replicas 🙏 ❤️
The text was updated successfully, but these errors were encountered: