| Summary: | monitoring notification seems same no matter how you set "Message Format" in notification method | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Jan Hutař <jhutar> |
| Component: | Monitoring | Assignee: | Grant Gainey <ggainey> |
| Status: | CLOSED WONTFIX | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 570 | CC: | dyordano, tlestach |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-28 18:34:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Monitoring has a number of issues, and is being removed in the upcoming SATELLITE-5.8 release. Closing, WONTFIX |
Description of problem: Monitoring notification seems same no matter how you set "Message Format" in notification method Version-Release number of selected component (if applicable): spacewalk-java-2.3.8-123.el6sat.noarch spacewalk-monitoring-2.2.1-1.el6sat.noarch How reproducible: always Steps to Reproduce: 1. Users -> <admin> -> Notification Methods -> Panic Destination Make sure "Message Format:" is checked (i.e. "Short (Pager-Style) Messages" is selected) 2. Monitor some system with "Linux: Load" probe and configure it this way: Probe Notifications: checked Notification Interval: 1 minute Notification Method: Panic Destination Probe Check Interval: 1 minute CPU Load 1-Minute Average Critical if above: 2 CPU Load 1-Minute Average Warn if above: 1 3. Make sure you go from OK state to WARNING or CRITICAL E.g. by running few `while true; do true; done &` on the client 4. Check email monitoring sends in a while about entering new state 5. Remove the load source on the client and let the Satellite notice we are in OK state again 6. Change notification method by unchecking "Message Format:" 7. Generate load again and check email Monitoring sends now Actual results: Email body have only this all the time: WARNING: <fqdn>: Linux: Load at 09:16 GMT, notification 01g9h5rb Expected results: Either message format should differ, or the form field can be removed as redundant (it does not change anything). Additional info: I might be missing some use case when this actually cause a difference (?)