Ceilometer alarm notifier did not send out HTTPs POST to HEAT-api-cfn [closed]

asked 2016-11-15 02:29:32 -0500

chao_w gravatar image

I created stack to auto scaling purpose, within this stack, one alarm in ceilometer had been created as well.

I was using HTTPs in alarm action url, and also configured the rest_notifier_certificate_key and rest_notifier_certificate_file in Ceilometer, after then I restarted all ceilometer services in order to apply the changes.

When alarm was raising, I did not see any the HTTPs POST be received in HEAT-api-cfn, besides, acrroding to the alarm notifier log, it seems the action had been executed, but no place to check the result.

Can anyone help me out?

2016-11-15T16:36:00.722303+09:00 controllor ceilometer-alarm-notifier Notifying alarm 38206816-5086-46f2-a22d-f545af3af279 with action SplitResult(scheme=u'https', netloc=u'controller:8000', path=u'/v1/signal/arn%3Aopenstack%3Aheat%3A%3A4d83b55bb9534333b42e085840bac9c2%3Astacks%2FserverScaling%2Fc9978657-af04-419e-ad1b-d4d9401bb91c%2Fresources%2Fserver_scaleup_policy', query=u'Timestamp=2016-11-15T05%3A28%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=a0dd4ab4ab1849b1ade70b5880088ae3&SignatureVersion=2&Signature=9jbnEyws6H4Td2LSCzLQdgzbXaiByWYDlSCq1Y3D3J4%3D', fragment='')

2016-11-15T16:36:00.722694+09:00 controllor ceilometer-alarm-notifier Notifying alarm serverScaling-cpu_alarm_high-bc6j5rgf2hct 38206816-5086-46f2-a22d-f545af3af279 from alarm to alarm with action SplitResult(scheme=u'https', netloc=u'controller:8000', path=u'/v1/signal/arn%3Aopenstack%3Aheat%3A%3A4d83b55bb9534333b42e085840bac9c2%3Astacks%2FserverScaling%2Fc9978657-af04-419e-ad1b-d4d9401bb91c%2Fresources%2Fserver_scaleup_policy', query=u'Timestamp=2016-11-15T05%3A28%3A36Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=a0dd4ab4ab1849b1ade70b5880088ae3&SignatureVersion=2&Signature=9jbnEyws6H4Td2LSCzLQdgzbXaiByWYDlSCq1Y3D3J4%3D', fragment='') because Remaining as alarm due to 1 samples outside threshold, most recent: 26.55. request-id: req-c4535c62-4486-4744-b30f-44f386231ae1

edit retag flag offensive reopen merge delete

Closed for the following reason duplicate question by rbowen
close date 2016-11-30 08:48:32.053964

Comments

rbowen gravatar imagerbowen ( 2016-11-30 08:48:28 -0500 )edit