Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E8ABE101DC for ; Wed, 26 Feb 2014 04:36:22 +0000 (UTC) Received: (qmail 54046 invoked by uid 500); 26 Feb 2014 04:36:22 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 53952 invoked by uid 500); 26 Feb 2014 04:36:21 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 53930 invoked by uid 500); 26 Feb 2014 04:36:20 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 53923 invoked by uid 99); 26 Feb 2014 04:36:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Feb 2014 04:36:20 +0000 Date: Wed, 26 Feb 2014 04:36:20 +0000 (UTC) From: "Girish Chaudhari (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CLOUDSTACK-2697) cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 // podId:: 1 // clusterId:: null } MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Girish Chaudhari reassigned CLOUDSTACK-2697: -------------------------------------------- Assignee: Girish Chaudhari > cluster id in alert message is null {alertType:: 1 // dataCenterId:: 1 // podId:: 1 // clusterId:: null } > --------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-2697 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2697 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Management Server > Affects Versions: 4.2.0 > Reporter: prashant kumar mishra > Assignee: Girish Chaudhari > Priority: Minor > Fix For: 4.3.0 > > Attachments: logs.rar > > > Cluster id should not be null in Alert message. > Snippet of log > -------------------- > 2013-05-27 13:13:19,879 WARN [apache.cloudstack.alerts] (CapacityChecker:null) alertType:: 1 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: System Alert: Low Unallocated CPU in cluster cluster pod pod of availability zone pod > 2013-05-27 13:13:19,890 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Have already sent: 1 emails for alert type '1' -- skipping send email > 2013-05-27 13:13:19,954 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) System Alert: Low Unallocated CPU in cluster cluster2 pod pod of availability zone pod > 2013-05-27 13:13:19,954 DEBUG [cloud.alert.AlertManagerImpl] (CapacityChecker:null) Unallocated CPU is low, total: 9576 Mhz, used: 2000 Mhz (20.89%) > 2013-05-27 13:13:19,955 WARN [apache.cloudstack.alerts] (CapacityChecker:null) alertType:: 1 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: System Alert: Low Unallocated CPU in cluster cluster2 pod pod of availability zone pod -- This message was sent by Atlassian JIRA (v6.1.5#6160)