cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Parth Jagirdar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6253) Optimizing VR alerts getting algorithm
Date Fri, 11 Apr 2014 17:40:17 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966853#comment-13966853
] 

Parth Jagirdar commented on CLOUDSTACK-6253:
--------------------------------------------

Following was found in 4.4 MS Logs.

https://issues.apache.org/jira/browse/CLOUDSTACK-6391



> Optimizing VR alerts getting algorithm
> --------------------------------------
>
>                 Key: CLOUDSTACK-6253
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6253
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Virtual Router
>    Affects Versions: 4.4.0
>            Reporter: Harikrishna Patnala
>            Assignee: Harikrishna Patnala
>             Fix For: 4.4.0
>
>
> Need to improve the algorithm in getRouterAlerts.sh to address the corrupted logs lines
and to consider the backed up files while searching for alerts. To remove some unused statements.

> To introduce rollover strategy for routerServiceMonitor.log with maxsize of 10MB and
backup count to 5.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message