<?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 flow collector longest export exceeded in Security Analytics</title>
    <link>https://community.cisco.com/t5/security-analytics/flow-collector-longest-export-exceeded/m-p/5050421#M1036</link>
    <description>&lt;P&gt;What does it mean? -&amp;nbsp;flow collector longest export exceeded&lt;/P&gt;
&lt;P&gt;I have some allarms like that for my devices, maybe I need to increase intervals for monitor or exporter?&lt;/P&gt;</description>
    <pubDate>Tue, 26 Mar 2024 05:00:37 GMT</pubDate>
    <dc:creator>dijix1990</dc:creator>
    <dc:date>2024-03-26T05:00:37Z</dc:date>
    <item>
      <title>flow collector longest export exceeded</title>
      <link>https://community.cisco.com/t5/security-analytics/flow-collector-longest-export-exceeded/m-p/5050421#M1036</link>
      <description>&lt;P&gt;What does it mean? -&amp;nbsp;flow collector longest export exceeded&lt;/P&gt;
&lt;P&gt;I have some allarms like that for my devices, maybe I need to increase intervals for monitor or exporter?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 05:00:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/security-analytics/flow-collector-longest-export-exceeded/m-p/5050421#M1036</guid>
      <dc:creator>dijix1990</dc:creator>
      <dc:date>2024-03-26T05:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: flow collector longest export exceeded</title>
      <link>https://community.cisco.com/t5/security-analytics/flow-collector-longest-export-exceeded/m-p/5050798#M1038</link>
      <description>&lt;P&gt;In Cisco StealthWatch (or what we now call Secure Network Analytics - SNA), the message "flow collector longest export exceeded" indicates an issue with the flow collector's ability to process and export network flow data in a timely manner. Cisco SNA uses flow collectors to aggregate, analyze, and export flow data, such as NetFlow, sFlow, or IPFIX, which is sent by network devices like routers and switches.&lt;BR /&gt;When the system detects that the time taken to export the aggregated flow data has exceeded a predefined threshold, this message is generated. This could be due to various reasons, such as:&lt;BR /&gt;1. High volume of network traffic, leading to an overwhelming amount of flow data to be processed.&lt;BR /&gt;2. Performance issues with the flow collector itself, possibly due to hardware limitations or other resource constraints.&lt;BR /&gt;3. Network latency or connectivity issues affecting the timely export of data.&lt;BR /&gt;4. Misconfiguration or inefficiencies in the flow export settings.&lt;BR /&gt;To address this issue, consider the following steps:&lt;BR /&gt;1. Review the current load and performance of the flow collector to ensure it's not being overloaded.&lt;BR /&gt;2. Check network connectivity and latency to ensure there are no bottlenecks affecting data export.&lt;BR /&gt;3. Assess the configuration settings for flow export intervals and adjust them if necessary to handle the volume of data more effectively.&lt;BR /&gt;4. Consider scaling up resources for the flow collector if it's consistently hitting performance limits.&lt;BR /&gt;5. If the problem persists, contact Cisco support for further assistance in troubleshooting the issue.&lt;BR /&gt;It is important to resolve this issue promptly, as delays in flow data export can impact the accuracy and timeliness of network monitoring and threat detection in SNA.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2024 13:18:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/security-analytics/flow-collector-longest-export-exceeded/m-p/5050798#M1038</guid>
      <dc:creator>rocedar</dc:creator>
      <dc:date>2024-03-26T13:18:25Z</dc:date>
    </item>
    <item>
      <title>Re: flow collector longest export exceeded</title>
      <link>https://community.cisco.com/t5/security-analytics/flow-collector-longest-export-exceeded/m-p/5135016#M1064</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I encountered the same "flow collector longest export exceeded" alarm in Stealthwatch. Long duration exporters can potentially cause performance issues and inhibit effective network visibility.&lt;/P&gt;&lt;P&gt;My configuration for NetFlow monitoring appears to be correct and aligns with the recommended practices outlined in the Cisco NetFlow Configuration Guide. Here's a summary of my configuration:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;flow monitor IPv4_NetFlow
 export exporter NetFlow_TO_SW_FC
 cache timeout active 60
 record SW_FLOW_RECORD

flow monitor IPv4_NetFlow_OUTPUT
 export exporter NetFlow_TO_SW_FC
 cache timeout active 60
 record SW_FLOW_RECORD_OUTPUT&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Despite the correct configuration, I am still seeing alarms related to "flow collector longest export exceeded. The hardware is designed to support up to 120.000 Flows per Second and I have around 50.000 FPS on a daily basis.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Jesús Ángel.&lt;/P&gt;</description>
      <pubDate>Sun, 23 Jun 2024 19:48:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/security-analytics/flow-collector-longest-export-exceeded/m-p/5135016#M1064</guid>
      <dc:creator>JesusAngel</dc:creator>
      <dc:date>2024-06-23T19:48:18Z</dc:date>
    </item>
  </channel>
</rss>

