Geeta,
The flow control event in 13.10 is not a very reliable way to assess the frequency or even the presence of flow control on the AMPs. That is because it does not use the flow control time metric from the SAWT table, as the flow control event does in 14.10. It uses the FlowControlled metric, which only reflects the state of the AMP at the end of the logging interval. It will not tell you how often AMPs go into flow control. So there will be many episodes of flow control that will be missed by FlowControlled.
I would suggest you think about using the AMP worker task event instead of the flow control event. If you pay attention to when you run out of AMP worker tasks and take action when you do, you will never get into flow control conditions, or rarely get into them. Therefore you would not need the flow control event.
Thanks, -Carrie
Geeta,
The flow control event in 13.10 is not a very reliable way to assess the frequency or even the presence of flow control on the AMPs. That is because it does not use the flow control time metric from the SAWT table, as the flow control event does in 14.10. It uses the FlowControlled metric, which only reflects the state of the AMP at the end of the logging interval. It will not tell you how often AMPs go into flow control. So there will be many episodes of flow control that will be missed by FlowControlled.
I would suggest you think about using the AMP worker task event instead of the flow control event. If you pay attention to when you run out of AMP worker tasks and take action when you do, you will never get into flow control conditions, or rarely get into them. Therefore you would not need the flow control event.
Thanks, -Carrie