[
https://issues.apache.org/jira/browse/CLOUDSTACK-6724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-6724.
-------------------------------------------
Resolution: Invalid
"Iteration" in your case is not CS specific iteration. For a cloudstack, that
would be the "try" - when you actually try to execute startRouter command. If
the command fails, the Alert is generated. So thats the correct behavior to
generate an alert per each non-successful API execution.
> Generate only alert message in MS for an iteration in router vm
> ----------------------------------------------------------------
>
> Key: CLOUDSTACK-6724
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6724
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.4.0
> Reporter: prashant kumar mishra
> Assignee: Alena Prokharchyk
> Fix For: 4.4.0
>
>
> Monitor script will try to start a process if it is not in running state, For
> each iteration it will try N times(depend on config value in script) , for
> each try we are writing logs but after iteration if process dint come up
> alert message is getting generated in logs , and we are sending each info in
> log to MS alerts ideally we should summarize log for each iteration and then
> send it to MS
> currently in CS
> =============
> alert is getting generated for each try i.e multiple alerts per iteration
> Requested
> ==========
> ->we can summarize the alert message for each iteration .Like" N tires but
> not able to restart xyz services"
> -->if service get started in some trial we can just say "service started
> after N trial"
--
This message was sent by Atlassian JIRA
(v6.2#6252)
