Support Questions
Find answers, ask questions, and share your expertise

Ambari alerts

Ambari alerts

Hi,

I am getting this error from both Active and StandBy node.

No Under Replicated Blocks

No failed Disk Volumes.

This service-level alert is triggered if the increase in storage capacity usage deviation has grown beyond the specified threshold within a week period.
6 REPLIES 6

Re: Ambari alerts

Rising Star

Can you click on the alerts and put the screenshot here for it for details ?

Can you see if this discussion helps you ?

https://community.hortonworks.com/questions/65555/hdfs-storage-capacity-usage-alert.html

Re: Ambari alerts

Re: Ambari alerts

Rising Star

@Sam Red

Thanks for the screenshot. Need more clarity. Given that you are saying that you are getting the error :

No Under Replicated Blocks
No failed Disk Volumes.

Are you getting this error in alert ?

A working alerts (HEALTH/CRITICAL/WARN) looks like this (sample)

Refer instance and response section.

screen-shot-2017-09-11-at-31904-pm.png

Can I have the full screenshot having instance and response section ?

Re: Ambari alerts

@Swapan Shridhar

The variance for this alert is 2,240,642,366B which is 25% of the 8,925,205,907B average (1,785,041,181B is the limit)



38607-alert.jpg

Re: Ambari alerts

Rising Star
The variance for this alert is 2,240,642,366B which is 25% of the 8,925,205,907B average (1,785,041,181B is the limit)

Given that its coming as CRITICAL alert, this doesn't match with 50% growth rate mentioned in alert as per the 1st screenshot. This doesn't look correct, as its assuming CRITICAL threshold to be less than 25%.

Can you enable and disable the alerts once, if that refreshes ?

Re: Ambari alerts

Expert Contributor

@Sam Red

There have been some issues fixed in the metric based alert script. What version of Ambari is this?

Can you attach the response for the following metrics GET call?

http:<METRICS_COLLECTOR_HOST>:6188/ws/v1/timeline/metrics?

metricNames=dfs.FSNamesystem.CapacityUsed&
appId=namenode&
hostname=<namenode_host>,<standby_namenode_host>&
startTime=<current_time - 7days>&
endTime=<current_time>

The start and end times can be specified in milliseconds using the link : http://www.ruddwire.com/handy-code/date-to-millisecond-calculators/#.WbrI_tOGOqA