A remote syslog is a good option, too. The method depends on the specific needs, resources, and infrastructure. Remote Syslog can be easier to set up. External logging solutions scale better, offer more analytical features, and can allocate more resources to log management. Try testing these approaches in a staging environment to assess their impact on performance and to ensure they meet compliance needs. That will be the best approach to determine the most beneficial solution. Kind regards, Sondra Sent from my iPhone > On Feb 23, 2024, at 6:29 AM, Bruce Momjian <bruce@xxxxxxxxxx> wrote: > > On Thu, Feb 22, 2024 at 08:54:52PM -0800, S Hoffman wrote: >> Hi Lucio Chiessi, >> >> Dealing with large volumes of data can be a challenging task. If you struggle >> with this issue, one possible solution is to consider using external logging >> services. Specifically, asynchronous logging services or external logging >> services that are designed to handle streaming data may be effective options to >> explore. Some popular external logging services in this regard include >> Elasticsearch and Spunk, known for their ability to handle large volumes of >> data. If you have any questions or want to explore other options, please let me >> know. > > Would remote syslog be an option too? > > -- > Bruce Momjian <bruce@xxxxxxxxxx> https://momjian.us > EDB https://enterprisedb.com > > Only you can decide what is important to you.
