TABLE OF CONTENTS

  • Overview
  • Checking Netagent logs
  • Solution


Overview

 You will notice that some access events are missing on the Banyan command center. This might happen when Banyan rate limiting is triggered due to the number of access events generated.

Banyan has two types of Access Events rate limiting. One is based on the total number of access events generated and the other one is based on the access events generated per key(base on user and device).

You can click here for more information about the Access events rate-limiting and its parameters.


Checking Netagent logs


To confirm the missing access events are due to rate limiting, check the logs on your Access Tier.


If the rate-limiting is due to the total access events generated, you can use the following filter on the netagent.log :
grep "filtered out access event due to no credit" /var/log/banyan/netagent.log



If the rate-limiting is due to the access events generated per key/userid, you can use the following filter on the netagent.log : 

grep "filtered out unexpired access event" /var/log/banyan/netagent.log


Solution

To stop being rate limiting, you can go to the settings in the config.yaml file located in /opt/banyan and modify the rate-limiting parameters.

If rate limiting is due to the total number of access events, you can increase the following default parameters:

access_event_credits_max: 1000

access_event_credits_interval: 1m

access_event_credits_per_interval : 5

 

Keep increasing the values until you don't see are more error messages for rate limiting on the netagent logs.

For instance, if you see 260 events with 'no credit' in 1 minute, you can increase the  access_event_credits_per_interval  from 5 to 300 and the access_event_credits_max from 1000 to a higher number such as 2000.


If rate limiting is due because key, you can disable it by changing the following parameter from true to false:

access_event_key_limiting