MonitorWare Knowledge Base

Hi All,

We have been running into an issue with Loganalyzer where searches take an exceptionally log time on an inconstant basis. The search we are using is

datelastx:2 source:~pvsc,~ppdc

and it seems to take sub 1 sec sometimes and then on other times it takes 30 to 45 seconds to run the same query. We are running Adiscon LogAnalyzer Version 4.1.1. We are running against a MariaDB 10.0.24 database. we have 4 rsyslog servers feeding into the database all running rsyslog. I am wondering if this could be record locking related some how? Any suggestions?

In the config.php I have made the change:
$CFG['Sources']['Source1']['DBEnableRowCounting'] = false;

in the stanza:
$CFG['DefaultSourceID'] = 'Source1';

$CFG['Sources']['Source1']['ID'] = 'Source1';
$CFG['Sources']['Source1']['Name'] = 'My Syslog Source';
$CFG['Sources']['Source1']['ViewID'] = 'SYSLOG';
$CFG['Sources']['Source1']['SourceType'] = SOURCE_DB;
$CFG['Sources']['Source1']['DBTableType'] = 'monitorware';
$CFG['Sources']['Source1']['DBType'] = DB_MYSQL;
$CFG['Sources']['Source1']['DBServer'] = 'AAA.BBB.CCC.DDD';
$CFG['Sources']['Source1']['DBName'] = 'mastersyslog';
$CFG['Sources']['Source1']['DBUser'] = 'XXXX';
$CFG['Sources']['Source1']['DBPassword'] = 'YYYYYY';
$CFG['Sources']['Source1']['DBTableName'] = 'SystemEvents';
$CFG['Sources']['Source1']['DBEnableRowCounting'] = false;


Thanks,
Sean

• Pulling out your Hair?
• Wasting Time and Money?
• Deadline Approaching?

Well I think I figured out the problem, the search that was failing or timing out I guess would be a better term is

datelastx:2 source:~pvsc,~ppdc

however when I change it to

datelastx:2 source:pvsc,ppdc

it is much faster and I have seen no more timeouts. Does that sound like a reasonable expectation, or am I just being lucky?

Sean