Hi,

It's entirely possible that there is no way to accommodate your syslog requirements on our platform.

MySQL isn't the fastest way to store late amounts of data, and there are very real hard limits to performance when you're trying to store large numbers of rows.

If you have data older than 3 months in the table, remove to and see how it affects performance. If you don't, your data volume is probably too large to effectively handle in MySQL.

Adam.

Sent from BlueMail
On 26 Aug 2017, at 12:10, dorje2007@seznam.cz wrote:
Dear Adam

thank you for your message.
We need to keep the logs for at least 3 months, and collecting them from 150 Cisco devices. 
So there is no purpose to truncate the Syslog table, rather to tune it , to be able to use the Syslog messages.

Housekeeping is set to remove the messages older then 3 months

is it possible to do so ? ( mysql tuning, observium loading page , ... )
Thank you very much

greetigns

Hi,

At this point you probably need to truncate the syslog page, and then afterwards investigate the housekeeping pages on our website.

Housekeeping will remove excess logs and speed things up in general.

Adam.

Sent from BlueMail
On 26 Aug 2017, at 12:02, dorje2007@seznam.cz wrote:
Dears,

in my Observium, i have about 80M records in the  Syslog message. 
When i want to access it via Observium - Syslog page, it take about 10-15 minutes.

My HW is : 8 GB RAM, 8 cores, HyperV

Would you be so kind to let me know, how can i tune it ? Also the other pages of Observium are quite slow

Thank you


observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium