<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Use Cases Overview on S2AP Documentation</title><link>https://docs.selector.ai/docs/use-cases/</link><description>Recent content in Use Cases Overview on S2AP Documentation</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 19 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://docs.selector.ai/docs/use-cases/index.xml" rel="self" type="application/rss+xml"/><item><title>Alerts and Queryables for Device Reset</title><link>https://docs.selector.ai/docs/use-cases/device-reset/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><guid>https://docs.selector.ai/docs/use-cases/device-reset/</guid><description>&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/device-reset/images/selector-logo.png" alt="Selector Logo">&lt;/p>
&lt;h2 id="alerts-and-queryable-for-device-resets">Alerts and Queryable for Device Resets&lt;/h2>
&lt;p>&lt;strong>Outcome&lt;/strong>: Monitoring and alerting capabilities are enabled for Device Reset. Device reset KPI is about identifying when a device reboots. The feature is enabled for all the devices deployed in all environments.&lt;/p>
&lt;p>&lt;strong>Dashboard Example:&lt;/strong>&lt;/p>
&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/device-reset/images/public-device-reset-use-case-1-edited.png" alt="Dashdoard for Device Reset">&lt;/p>
&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/device-reset/images/public-device-reset-use-case-2-edited.png" alt="Dashdoard 2 for Device Reset">&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th style="text-align: left">Alert Name&lt;/th>
 &lt;th style="text-align: left">Priority&lt;/th>
 &lt;th style="text-align: left">Queryable&lt;/th>
 &lt;th style="text-align: left">Notes&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td style="text-align: left">Device Reboot&lt;/td>
 &lt;td style="text-align: left">P3&lt;/td>
 &lt;td style="text-align: left">device_reset_state_violation&lt;/td>
 &lt;td style="text-align: left">An alert is generated when the Device reboots.&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>As defined in RFC 1213, the &lt;strong>SNMP sysUpTime&lt;/strong> counter is a 32-bit value that peaks at &lt;strong>4,294,967,295&lt;/strong>. This represents approximately &lt;strong>497.1 days&lt;/strong> (specifically 497 days, 2 hours, 27 minutes, and 53 seconds). Once this limit is reached, the counter &amp;ldquo;wraps around&amp;rdquo; and automatically resets to zero.&lt;/p></description></item><item><title>Alerts and Queryables for Module Status</title><link>https://docs.selector.ai/docs/use-cases/module-status/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><guid>https://docs.selector.ai/docs/use-cases/module-status/</guid><description>&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/module-status/images/selector-logo.png" alt="Selector Logo">&lt;/p>
&lt;h2 id="alerts-and-queryable-for-module-status">Alerts and Queryable for Module Status&lt;/h2>
&lt;p>This use case establishes monitoring and alerting capabilities for Administrative state of &lt;strong>Field Replaceable Units (FRUs)&lt;/strong>—things like line cards, supervisor engines, or power supplies—within modular chassis devices deployed in various physical environments such as data centers or headquarters.&lt;/p>
&lt;p>&lt;strong>Scale of this example&lt;/strong>: 297 devices, 4 vendors( Cisco, Arista, Palo Alto and HP), with many different models.&lt;/p>
&lt;h2 id="dashboard-for-the-example">Dashboard for the Example&lt;/h2>
&lt;p>Alerts, including alarm codes, are configured and BigPanda is successfully receiving all configured alerts.&lt;/p></description></item><item><title>Configured Alerts for Load Balancers</title><link>https://docs.selector.ai/docs/use-cases/load-balancers/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://docs.selector.ai/docs/use-cases/load-balancers/</guid><description>&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/load-balancers/images/selector-logo.png" alt="Selector Logo">&lt;/p>
&lt;h2 id="configured-alerts-for-load-balancers">Configured Alerts for Load Balancers&lt;/h2>
&lt;p>Selector implements the following 5 alerts to monitor the health of Load Balancers. While these alerts will work for all F5 load balancers, for this example document, Selector has enabled these alerts only for two example devices : ABCDEFGHIJ01 and ABCDEFGHIJ02.&lt;/p>
&lt;p>This document describes the specific device conditions that trigger these alerts:&lt;/p>
&lt;h3 id="table-of-contents">Table of Contents&lt;/h3>
&lt;p>&lt;a href="https://docs.selector.ai/docs/use-cases/load-balancers/#alert-1-vipserveravailstate-down-alert-at-device-level">Alert 1: VIPServerAvailState &lt;strong>down&lt;/strong> alert at device level&lt;/a>&lt;/p></description></item><item><title>Alerts and Queryables for Cisco Stack Switch Monitoring</title><link>https://docs.selector.ai/docs/use-cases/cisco-stack-monitoring/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://docs.selector.ai/docs/use-cases/cisco-stack-monitoring/</guid><description>&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/cisco-stack-monitoring/images/selector-logo.png" alt="Selector Logo">&lt;/p>
&lt;h2 id="alerts-and-queryable-for-cisco-stack-switch-monitoring">Alerts and Queryable for Cisco Stack Switch Monitoring&lt;/h2>
&lt;p>This use case establishes monitoring and alerting capabilities for Cisco switch stacks deployed in various physical environments such as data centers or headquarters.&lt;/p>
&lt;p>&lt;strong>Scale of this example&lt;/strong>: 735 devices, including 80 switches in stacks and 655 switches as standalone.&lt;/p>
&lt;h2 id="configured-alert">Configured Alert&lt;/h2>
&lt;p>Alerts, including alarm codes, are configured and BigPanda is successfully receiving all configured alerts.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th style="text-align: left">Alert Name&lt;/th>
 &lt;th style="text-align: left">Priority&lt;/th>
 &lt;th style="text-align: left">Queryable&lt;/th>
 &lt;th style="text-align: left">Notes&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td style="text-align: left">CiscoStackMemberStatus&lt;/td>
 &lt;td style="text-align: left">P2&lt;/td>
 &lt;td style="text-align: left">cisco_stack_switch_status as line-plot where cisco_stack_switch_status_violation&amp;gt;0 group-by device&lt;/td>
 &lt;td style="text-align: left">An alert will be triggered if the state of the switch stack is not “ready” or “added”. State of the stack is polled via SNMP MIB cswSwitchState - 1.3.6.1.4.1.9.9.500.1.2.1.1.6&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/cisco-stack-monitoring/images/cisco-stack-public-image-1.png" alt="Cisco Stack Figure 1">&lt;/p></description></item><item><title>Alerts and Queryables for Firewall Monitoring</title><link>https://docs.selector.ai/docs/use-cases/firewall-monitoring/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://docs.selector.ai/docs/use-cases/firewall-monitoring/</guid><description>&lt;p>&lt;img src="https://docs.selector.ai/docs/use-cases/firewall-monitoring/images/selector-logo.png" alt="Selector Logo">&lt;/p>
&lt;h2 id="alerts-and-queryable-for-firewall-monitoring">Alerts and Queryable for Firewall Monitoring&lt;/h2>
&lt;p>This use case establishes monitoring and alerting capabilities for the &lt;strong>High Availability (HA)&lt;/strong> status for &lt;strong>critical&lt;/strong> &lt;strong>Checkpoint&lt;/strong> and &lt;strong>Palo Alto Firewalls&lt;/strong> deployed in various physical environments such as data centers or headquarters.&lt;/p>
&lt;p>&lt;strong>Scale of this Example:&lt;/strong> Checkpoint (11), and Palo Alto (150) devices are covered.&lt;/p>
&lt;h2 id="configured-example">&lt;strong>Configured Example&lt;/strong>&lt;/h2>
&lt;p>Alerts, including alarm codes, are configured and BigPanda is successfully receiving all configured alerts.&lt;/p>
&lt;h2 id="alerting-condition">&lt;strong>Alerting Condition&lt;/strong>&lt;/h2>
&lt;p>The alert triggers when there is a violation on Palo Alto or Checkpoint firewall HA status. The specifics are shown as shown in the following table.&lt;/p></description></item></channel></rss>