<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Exclude &amp;quot;ALERT&amp;quot; event type vol.wafl.full for specific volumes in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434343#M40485</link>
    <description>&lt;P&gt;We have an SVM setup for an internal customer who creates persistent volumes for k8s vms using the trident driver.&amp;nbsp; We have specific alerting setup for them in Active IQ that works for their needs, but we also use Ontap events for our purposes.&amp;nbsp;&amp;nbsp; Their volumes often fill up and then we get spammed with Ontap events for vol.wafl.full.&amp;nbsp;&amp;nbsp; Their volumes are created via the API and are added and removed as k8s vm's request resources, but they all volume names are prepended with "trident_pvc_"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example vol names:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;trident_pvc_836e672...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;trident_pvc_836e073...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;trident_pvc_836e332...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a way to exclude the event wafl.vol.full and match to only volumes that start with the string "trident_pvc"?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I do not want to to exclude all wafl.vol.full events&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This is what we currently use for a catch all:&lt;BR /&gt;Filter Name Rule Rule Message Name SNMP Trap Type Severity&lt;BR /&gt;Position Type&lt;BR /&gt;----------- -------- --------- ---------------------- --------------- --------&lt;BR /&gt;storageteam&lt;BR /&gt;10 include * * EMERGENCY, ALERT, ERROR&lt;BR /&gt;11 exclude * * *&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 10:01:43 GMT</pubDate>
    <dc:creator>bpostk</dc:creator>
    <dc:date>2025-06-04T10:01:43Z</dc:date>
    <item>
      <title>Exclude "ALERT" event type vol.wafl.full for specific volumes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434343#M40485</link>
      <description>&lt;P&gt;We have an SVM setup for an internal customer who creates persistent volumes for k8s vms using the trident driver.&amp;nbsp; We have specific alerting setup for them in Active IQ that works for their needs, but we also use Ontap events for our purposes.&amp;nbsp;&amp;nbsp; Their volumes often fill up and then we get spammed with Ontap events for vol.wafl.full.&amp;nbsp;&amp;nbsp; Their volumes are created via the API and are added and removed as k8s vm's request resources, but they all volume names are prepended with "trident_pvc_"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Example vol names:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;trident_pvc_836e672...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;trident_pvc_836e073...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;trident_pvc_836e332...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a way to exclude the event wafl.vol.full and match to only volumes that start with the string "trident_pvc"?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I do not want to to exclude all wafl.vol.full events&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;This is what we currently use for a catch all:&lt;BR /&gt;Filter Name Rule Rule Message Name SNMP Trap Type Severity&lt;BR /&gt;Position Type&lt;BR /&gt;----------- -------- --------- ---------------------- --------------- --------&lt;BR /&gt;storageteam&lt;BR /&gt;10 include * * EMERGENCY, ALERT, ERROR&lt;BR /&gt;11 exclude * * *&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:01:43 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434343#M40485</guid>
      <dc:creator>bpostk</dc:creator>
      <dc:date>2025-06-04T10:01:43Z</dc:date>
    </item>
    <item>
      <title>Re: Exclude "ALERT" event type vol.wafl.full for specific volumes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434347#M40488</link>
      <description>&lt;P&gt;I guess that modifying volume full thresholds would do the trick.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Check this out:&amp;nbsp;&lt;A href="https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_configure_Aggregate_and_Volume_Nearly_Full_and_Full_Thresholds_in_Clustered_Data_ONTAP_8_and_ONTAP_9" target="_blank"&gt;https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/How_to_configure_Aggregate_and_Volume_Nearly_Full_and_Full_Thresholds_in_Clustered_Data_ONTAP_8_and_ONTAP_9&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 17:10:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434347#M40488</guid>
      <dc:creator>pedro_rocha</dc:creator>
      <dc:date>2022-04-22T17:10:31Z</dc:date>
    </item>
    <item>
      <title>Re: Exclude "ALERT" event type vol.wafl.full for specific volumes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434349#M40490</link>
      <description>&lt;P&gt;That looks to be a global change across the cluster?&amp;nbsp; Which we wouldn't want to do, and some of these trident volumes can get to 100% at times before their checks kick in and push an expansion through the trident driver&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 17:15:29 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434349#M40490</guid>
      <dc:creator>bpostk</dc:creator>
      <dc:date>2022-04-22T17:15:29Z</dc:date>
    </item>
    <item>
      <title>Re: Exclude "ALERT" event type vol.wafl.full for specific volumes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434351#M40491</link>
      <description>&lt;P&gt;did you check the command?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;volume modify -volume VOL1...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You can change it on a per volume basis&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Apr 2022 17:25:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434351#M40491</guid>
      <dc:creator>pedro_rocha</dc:creator>
      <dc:date>2022-04-22T17:25:11Z</dc:date>
    </item>
    <item>
      <title>Re: Exclude "ALERT" event type vol.wafl.full for specific volumes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434387#M40504</link>
      <description>&lt;P&gt;Good to know, thanks.&amp;nbsp; As these volumes are created and destroyed dynamically, hopefully that is something that can be set with the trident driver.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Apr 2022 16:09:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Exclude-quot-ALERT-quot-event-type-vol-wafl-full-for-specific-volumes/m-p/434387#M40504</guid>
      <dc:creator>bpostk</dc:creator>
      <dc:date>2022-04-25T16:09:46Z</dc:date>
    </item>
  </channel>
</rss>

