log notifier's output is not well organized

[Lianhao Lu]

For log aodh notifier, the output message is not well organized, see the following example:

2016-12-08 15:48:58.359 INFO aodh.notifier.log [-] Notifying alarm cpu_l3_cache d53d4dd7-27c5-4508-a5da-c6c2c6890206 of low priority from alarm to alarm with action SplitResult(scheme=u'log', netloc=u'', path=u'', query='', fragment='') because Remaining as alarm due to 1 samples outside threshold, most recent: 270336.0.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/408977

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/408977
Committed: https://git.openstack.org/cgit/openstack/aodh/commit/?id=d0fd8525773d82808ade2244740256b5621f7521
Submitter: Jenkins
Branch: master

commit d0fd8525773d82808ade2244740256b5621f7521
Author: Lianhao Lu <email address hidden>
Date: Fri Dec 9 14:42:18 2016 +0800

    Change for more useful output in log notifier

    Modified the log notifier output to be more usefule, since the action
    parameter in the log notifier is a SplitResult object, we need to change
    the output more readable.

    Change-Id: I320f937d389f60a11bde767b2f4025df0008ce32
    Closes-Bug: #1648334

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/aodh 4.0.0 release.