Hello, I'm not sure I understand your question. If you're talking about performance provided by various services for aggregating logs - that shouldn't be your problem. They need to be able to ingest logs at the rate you send them. Provided that you buy a big enough plan to handle those logs.
If you're talking about rsyslog's performance, I would need more details on your setup to recommend something. Here's a nice link about most of rsyslog's configuration parameters: http://www.rsyslog.com/doc/rsyslog_conf_global.html Defaults are pretty sensible, but if you move lots of logs around, you might want to increase some settings around your queues. To understand what queues are about, take a look at this article: 2013/4/15 Mayur Patil <[email protected]> > Hello Sir, > > One more question which are parameters on which we can test performance > ?? > > In your opinion. which one should I use faster implementations ?? > > Seeking for guidance, > > Thank you!! > > You can store your logs locally, for example on a central server in your > > network, or you can send them to a service that can store those logs for > > you, like PaperTrail, or Loggly, or Splunk Storm or... > > > > Best regards, > > Radu > > > > -- > *Cheers, > Mayur*. > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
