{"id":3499,"date":"2021-07-13T10:38:37","date_gmt":"2021-07-13T10:38:37","guid":{"rendered":"https:\/\/wiki.thomasandsofia.com\/?p=3499"},"modified":"2021-08-20T15:55:21","modified_gmt":"2021-08-20T15:55:21","slug":"service-impact","status":"publish","type":"post","link":"https:\/\/wiki.thomasandsofia.com\/?p=3499","title":{"rendered":"Service Impact"},"content":{"rendered":"<p>Service Impact<\/p>\n<h1><span style=\"color: #ff0000;\">To Do<\/span><\/h1>\n<ul>\n<li>Understand Process Sets<\/li>\n<li>Monitor II<\/li>\n<\/ul>\n<h1>Resources<\/h1>\n<ul>\n<li>Lab\n<ul>\n<li><a href=\"https:\/\/zenoss5.train1.zenoss.com\" target=\"_blank\" rel=\"noopener\">https:\/\/zenoss5.train1.zenoss.com<\/a><\/li>\n<li>training:Z&#8230;123<\/li>\n<\/ul>\n<\/li>\n<li>Video: <a href=\"https:\/\/s3.us-east-2.amazonaws.com\/s3.thomasandsofia.com\/zenoss\/training\/service-impact\/20200528-Zenoss_Service_Impact.mp4\" target=\"_blank\" rel=\"noopener\">https:\/\/s3.us-east-2.amazonaws.com\/s3.thomasandsofia.com\/zenoss\/training\/service-impact\/20200528-Zenoss_Service_Impact.mp4<\/a><\/li>\n<li><a href=\"https:\/\/s3.us-east-2.amazonaws.com\/s3.thomasandsofia.com\/zenoss\/training\/service-impact\/Zenoss+Service+Impact+Training+Slides.5.2.3-ILT-V1.1.pdf\" target=\"_blank\" rel=\"noopener\">Training Slides<\/a><\/li>\n<li><a href=\"https:\/\/s3.us-east-2.amazonaws.com\/s3.thomasandsofia.com\/zenoss\/training\/service-impact\/Zenoss+Service+Impact+Training+Student+Exercise+Guide.5.2.3-ILT-V1.1.pdf\" target=\"_blank\" rel=\"noopener\">Exercise Guide<\/a><\/li>\n<\/ul>\n<h1>What is Service Impact (Impact for short)<\/h1>\n<ul>\n<li>Resource Manager tells you what happened<\/li>\n<li>Impact tells you why you should care\n<ul>\n<li>By building an Impact Service, you can tell what effect an event is going to have on a service downstream.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Benefits<\/h2>\n<ul>\n<li>Constantly updated service events \/\u00a0 status<\/li>\n<li>Automated root cause analysis<\/li>\n<li>Enhanced event management\n<ul>\n<li>If a member of a service has an event, an event is also generated for the service.\n<ul>\n<li><code>\/Service\/<\/code> event class<\/li>\n<\/ul>\n<\/li>\n<li>By creating triggers and notifications only on Dynamic Services, you will reduce the amount of event &#8220;noise&#8221;<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1>How it works<\/h1>\n<ul>\n<li>Based on devices in Resource Manager and events generated by these devices.<\/li>\n<li>Adds 2 new services\n<ul>\n<li>Impact:\n<ul>\n<li>State propagation<\/li>\n<li>provides service alerting and root cause analysis<\/li>\n<\/ul>\n<\/li>\n<li>zenimpactstate:\n<ul>\n<li>Performs state calculations and event filtering for the Impact service.<\/li>\n<\/ul>\n<\/li>\n<li>Add Graph Database\n<ul>\n<li>All devices in the Object Database are copied\/replicated into the Graph database.<\/li>\n<li>Add relationships between service elements and the state of each element<\/li>\n<li>Built for speed.\u00a0 Does not bog down the object database.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1>How the Graph database works<\/h1>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/graphmq.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3503\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/graphmq.png\" alt=\"\" width=\"967\" height=\"736\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/graphmq.png 967w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/graphmq-300x228.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/graphmq-768x585.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/graphmq-150x114.png 150w\" sizes=\"auto, (max-width: 967px) 100vw, 967px\" \/><\/a><\/p>\n<ul>\n<li>Services are built on Members (aka Nodes in the database).\n<ul>\n<li>Nodes have properties\n<ul>\n<li>Node type : Service, Device, etc.<\/li>\n<li>Availability State<\/li>\n<li>Performance State<\/li>\n<li>Production State &#8230;<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Relationships bubble up.\u00a0 Underlying events bubble to higher (Parent Nodes) to the top node.<\/li>\n<\/ul>\n<h1>Service States (aka Impact Types) and State Mappings<\/h1>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/EventSeverityMapping.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3506\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/EventSeverityMapping.png\" alt=\"\" width=\"974\" height=\"429\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/EventSeverityMapping.png 974w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/EventSeverityMapping-300x132.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/EventSeverityMapping-768x338.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/EventSeverityMapping-150x66.png 150w\" sizes=\"auto, (max-width: 974px) 100vw, 974px\" \/><\/a><\/p>\n<ul>\n<li>Two Impact Types &#8211; Availability and Performance\n<ul>\n<li>Availability Health\n<ul>\n<li>Up (Clear, Debug, Info)<\/li>\n<li>At Risk (Warning)<\/li>\n<li>Degraded (Error)<\/li>\n<li>Down (Critical)<\/li>\n<\/ul>\n<\/li>\n<li>Performance Health\n<ul>\n<li>Acceptable (Clear)<\/li>\n<li>Degraded (Warning, Error)<\/li>\n<li>Unacceptable (Critical)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Type of Impact is determined by an event&#8217;s Event Class\n<ul>\n<li>Anything with <code>\/Status\/<\/code> will be categorized under Availability<\/li>\n<li>Anything with <code>\/Perf\/<\/code> will be categorized under Performance<\/li>\n<\/ul>\n<\/li>\n<li>The State of the impacted element is derive3d from the Event Severity\n<ul>\n<li>It is Important that template Thresholds are configured accurately.<\/li>\n<li>If Thresholds are too broad or too narrow, the Impact State will be inaccurate.<\/li>\n<\/ul>\n<\/li>\n<li>By default, a Service&#8217;s state is the most severe state of any of its constituent members.<\/li>\n<\/ul>\n<h1>Building Services<\/h1>\n<ul>\n<li>A Dynamic Service is a collection of Members.<\/li>\n<li>Service members may consist of\n<ul>\n<li>Devices<\/li>\n<li>Components\n<ul>\n<li>When adding a component, you get the rest of the device as a dependent part \/ related member of that service<\/li>\n<\/ul>\n<\/li>\n<li>Other Services<\/li>\n<li>Logical Nodes<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Events<\/h2>\n<ul>\n<li>When an event occurs on a Member, an event will also be generated against the Service&#8217;s Availability or Performance.<\/li>\n<li>Events are &#8216;scored&#8217; with a Confidence value which will show which event is most likely to cause the problem.\n<ul>\n<li>Generally, the farther down in the chain an event occurs, the higher the confidence score will be.<\/li>\n<li>If a database is down, and that database is built on a VM that is also down, we should probably spend our time looking into the VM.<\/li>\n<\/ul>\n<\/li>\n<li>58:00<\/li>\n<\/ul>\n<h1>Server Component Monitoring<\/h1>\n<p>1:07:00<\/p>\n<h2>Process Monitoring<\/h2>\n<p>1:19:00<\/p>\n<h2>Application Monitoring<\/h2>\n<p>1:39:00<\/p>\n<h1>Other Dynamic Services<\/h1>\n<p>1:46:00<\/p>\n<p>Building services out of services.<\/p>\n<h1>Monitoring WebSites<\/h1>\n<p>2:21:00<\/p>\n<p>Creating &#8220;dummy devices&#8221;<\/p>\n<ul>\n<li>Do not have an IP Address<\/li>\n<li>Do not have a default monitoring template<\/li>\n<li>Names do not resolve in DNS\n<ul>\n<li>site-blog.domain.tld<\/li>\n<\/ul>\n<\/li>\n<li>Use Custom Properties to add the IP address<\/li>\n<li>Add required local copies of the required monitoring templates<\/li>\n<li>Edit the template to use the cProp vs. zProp.<\/li>\n<\/ul>\n<h1>Navigating Impact View<\/h1>\n<ul>\n<li>Right click on a node to see Child Services<\/li>\n<li>Right click on the white space for Show All<\/li>\n<\/ul>\n<h1>Root Cause Analysis &amp; Confidence Scores<\/h1>\n<p>2:39:00<\/p>\n<ul>\n<li>Visible only in the Impact Events view<\/li>\n<li>Use the Confidence scores.\u00a0 Highest score likely your root cause.<\/li>\n<li>Rating auto-magically applies.\n<ul>\n<li>Down (Critical) will rank higher than Degraded or At Risk\n<ul>\n<li>This can be altered by creating a <strong>Service Policy<\/strong>.\u00a0 See below<\/li>\n<\/ul>\n<\/li>\n<li>The lower in the chain (closer to the hardware, sort of) will often rank higher than events higher up.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1>Synthetic Web Transactions using Twill<\/h1>\n<p>2:42:00<\/p>\n<h1>Logical Nodes<\/h1>\n<p>2:46:00<\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnode-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3512\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnode-1.png\" alt=\"\" width=\"994\" height=\"698\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnode-1.png 994w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnode-1-300x211.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnode-1-768x539.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnode-1-150x105.png 150w\" sizes=\"auto, (max-width: 994px) 100vw, 994px\" \/><\/a><\/p>\n<ul>\n<li>Logical Nodes are similar to Triggers\n<ul>\n<li>You define the criteria that sets them.<\/li>\n<\/ul>\n<\/li>\n<li>Often used for events that do not fall under the \/Status\/ or \/Perf\/ event classes.\n<ul>\n<li>Hint: Look at Event Classes to see all of the classes that are not \/Status\/ and \/Perf\/<\/li>\n<li>Example: Event class \/Capacity\/ for a Predictive Threshold event for a hard disk.<\/li>\n<li>When setting the Availability or Performance states, use the class (Availability or Performance) the event would fall under.\n<ul>\n<li>In the example above, running out of disk space would eventually become a \/Perf\/ event.<\/li>\n<\/ul>\n<\/li>\n<li>This can be thought of as mapping non-\/Status\/ and non-\/Perf\/ events to \/Status\/ or \/Perf\/<\/li>\n<\/ul>\n<\/li>\n<li>These can then be added as Members to any Dynamic Service<\/li>\n<\/ul>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnodeaddmember.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3513\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnodeaddmember.png\" alt=\"\" width=\"761\" height=\"537\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnodeaddmember.png 761w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnodeaddmember-300x212.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/logicalnodeaddmember-150x106.png 150w\" sizes=\"auto, (max-width: 761px) 100vw, 761px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<h1>Service Policies<\/h1>\n<ul>\n<li>By default, all Dynamic Services fall under the Default Service Policy<\/li>\n<li><strong>Global Policies<\/strong> apply to all nodes above the affected node<\/li>\n<li><strong>Contextual Policies<\/strong> apply to ONLY the Parent node and are not propagated up.<\/li>\n<\/ul>\n<h2>Service Policies Overview<\/h2>\n<ul>\n<li>Collection of State Triggers.\u00a0 The conditions under which the state of a Service or Member element changes.\n<ul>\n<li>Example:\n<ul>\n<li>Critical events cause the Dynamic Services state to be critical&#8230;<\/li>\n<li>Don&#8217;t mark degraded unless 50% or more of (Member Set) are degraded<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Applied to a service or any of its elements<\/li>\n<li>Assist in root cause identification<\/li>\n<li>Provide multiple availability and performance states<\/li>\n<li>Provide event storm filtering, roll-up and windowing<\/li>\n<li>Can be applied globally or contextually<\/li>\n<li>State of impacting elements rolled up into state of impacted element, worst resulting state takes precedence.<\/li>\n<\/ul>\n<h2>How to Configure a Service Policy: Cluster Example<\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ServicePolicyCluster.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3514\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ServicePolicyCluster.png\" alt=\"\" width=\"580\" height=\"338\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ServicePolicyCluster.png 580w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ServicePolicyCluster-300x175.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ServicePolicyCluster-150x87.png 150w\" sizes=\"auto, (max-width: 580px) 100vw, 580px\" \/><\/a><\/p>\n<ul>\n<li>Cluster 1 Servers &gt; Impact View<\/li>\n<li>Ensure Aspect = Availability<\/li>\n<li>Cluster 1 Servers &gt; Right Click &gt; Edit Impact Policies<\/li>\n<\/ul>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureServicePolicies.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3515\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureServicePolicies.png\" alt=\"\" width=\"799\" height=\"231\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureServicePolicies.png 799w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureServicePolicies-300x87.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureServicePolicies-768x222.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureServicePolicies-150x43.png 150w\" sizes=\"auto, (max-width: 799px) 100vw, 799px\" \/><\/a><\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureImpactPolicies.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3516\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureImpactPolicies.png\" alt=\"\" width=\"603\" height=\"303\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureImpactPolicies.png 603w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureImpactPolicies-300x151.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/ConfigureImpactPolicies-150x75.png 150w\" sizes=\"auto, (max-width: 603px) 100vw, 603px\" \/><\/a><\/p>\n<h3>Policy Applied<\/h3>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/PolicyApplied.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3518\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/PolicyApplied.png\" alt=\"\" width=\"230\" height=\"225\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/PolicyApplied.png 230w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/PolicyApplied-150x147.png 150w\" sizes=\"auto, (max-width: 230px) 100vw, 230px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<h2>Events Applied<\/h2>\n<p><strong>25% of servers down = No Change<\/strong><\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/1serverdown.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3519\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/1serverdown.png\" alt=\"\" width=\"657\" height=\"249\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/1serverdown.png 657w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/1serverdown-300x114.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/1serverdown-150x57.png 150w\" sizes=\"auto, (max-width: 657px) 100vw, 657px\" \/><\/a><\/p>\n<p><strong>50% of servers down = At Risk<\/strong><\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/2serverdown.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3520\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/2serverdown.png\" alt=\"\" width=\"658\" height=\"240\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/2serverdown.png 658w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/2serverdown-300x109.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/2serverdown-150x55.png 150w\" sizes=\"auto, (max-width: 658px) 100vw, 658px\" \/><\/a><\/p>\n<p><strong>75% of servers down = Degraded<\/strong><\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/3serverdown.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3521\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/3serverdown.png\" alt=\"\" width=\"657\" height=\"234\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/3serverdown.png 657w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/3serverdown-300x107.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/3serverdown-150x53.png 150w\" sizes=\"auto, (max-width: 657px) 100vw, 657px\" \/><\/a><\/p>\n<p><strong>100% of servers down = Down<\/strong><\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/4serverdown.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3522\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/4serverdown.png\" alt=\"\" width=\"657\" height=\"233\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/4serverdown.png 657w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/4serverdown-300x106.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/4serverdown-150x53.png 150w\" sizes=\"auto, (max-width: 657px) 100vw, 657px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<h1>Dashboard Portlet<\/h1>\n<ul>\n<li>Quick view of Dynamic Services&#8217; States<\/li>\n<li>Can be narrowed down by selecting an Organizer<\/li>\n<\/ul>\n<p><strong>Edit View<\/strong><\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletedit.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3526\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletedit.png\" alt=\"\" width=\"806\" height=\"407\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletedit.png 806w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletedit-300x151.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletedit-768x388.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletedit-150x76.png 150w\" sizes=\"auto, (max-width: 806px) 100vw, 806px\" \/><\/a><\/p>\n<p><strong>Dashboard View<\/strong><\/p>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletview.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3527\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletview.png\" alt=\"\" width=\"480\" height=\"224\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletview.png 480w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletview-300x140.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dashportletview-150x70.png 150w\" sizes=\"auto, (max-width: 480px) 100vw, 480px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<h1>Impact Triggers and Notifications<\/h1>\n<h2>Triggers<\/h2>\n<ul>\n<li>Triggers can test for events in the Service event class<\/li>\n<li>One use case for this are Atos Collector Failovers\n<ul>\n<li>When all delegate hosts in a collector are down, a trigger enables a Command notification that runs a script to move all devices to the backup collector.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/atostrigger.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3528\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/atostrigger.png\" alt=\"\" width=\"837\" height=\"450\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/atostrigger.png 837w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/atostrigger-300x161.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/atostrigger-768x413.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/atostrigger-150x81.png 150w\" sizes=\"auto, (max-width: 837px) 100vw, 837px\" \/><\/a><\/p>\n<h2>Notifications<\/h2>\n<p><strong>Notification type: SNMP Trap &#8211; Impact<\/strong><\/p>\n<ul>\n<li>Impact also includes a new Impact MIB<\/li>\n<li>These notifications will send SNMP Traps that can be decoded with this MIB<\/li>\n<li>Usage is very rare, but available<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h1>Tips and Tricks<\/h1>\n<h2>Add Devices by Device Organizer<\/h2>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dynamicserviceorganizer.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-3525\" src=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dynamicserviceorganizer.png\" alt=\"\" width=\"730\" height=\"433\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dynamicserviceorganizer.png 730w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dynamicserviceorganizer-300x178.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2021\/07\/dynamicserviceorganizer-150x89.png 150w\" sizes=\"auto, (max-width: 730px) 100vw, 730px\" \/><\/a><\/p>\n<ul>\n<li>If you have automation that automatically adds\/creates VMs that also adds them to Zenoss Monitoring and assigns them to a Device Organizer (Example: Systems &gt; Clusters &gt; Web), you can simply add the Organizer as a Member of a Dynamic Service.<\/li>\n<li>This prevents the need to continually add\/remove devices manually.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Best Practices<\/h2>\n<ul>\n<li>Create reusable Dynamic Services often.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Service Impact To Do Understand Process Sets Monitor II Resources Lab https:\/\/zenoss5.train1.zenoss.com training:Z&#8230;123 Video: https:\/\/s3.us-east-2.amazonaws.com\/s3.thomasandsofia.com\/zenoss\/training\/service-impact\/20200528-Zenoss_Service_Impact.mp4 Training Slides Exercise Guide What is Service Impact (Impact for short) Resource Manager tells you what happened Impact tells you why you should care By building an Impact Service, you can tell what effect an event is going to have ..<\/p>\n<div class=\"clear-fix\"><\/div>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/?p=3499\" title=\"read more...\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[59],"tags":[],"class_list":["post-3499","post","type-post","status-publish","format-standard","hentry","category-zenoss"],"_links":{"self":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/3499","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3499"}],"version-history":[{"count":18,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/3499\/revisions"}],"predecessor-version":[{"id":3598,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/3499\/revisions\/3598"}],"wp:attachment":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3499"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3499"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3499"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}