I have a question about the fpolicy counters in cDOT. int the TR-4429_FPolicy for cDOT-Varonis, there are two objects: fpolicy and fpolicy_server. They both have some counters such as max_request_latency, outstanding_requests, etc. What is the difference between fpolicy and fpolicy_server?
statistics show -object fpolicy –instance <instance_name> -sample-id <id> statistics show -object fpolicy_server –instance <instance_name> -sample-id <id>
Table 6) List of FPolicy counters. max_request_latency Maximum screen requests latency outstanding_requests Total number of screen requests in process request_latency_hist Histogram of latency for screen requests requests_dispatched_rate Number of screen requests dispatched per second requests_received_rate Number of screen requests received per second
Table 7) List of fpolicy_server counters. max_request_latency Maximum latency for a screen request outstanding_requests Total number of screen requests waiting for response request_latency Average latency for screen request request_latency_hist Histogram of latency for screen requests request_sent_rate Number of screen requests sent to FPolicy server per second response_received_rate Number of screen responses received from FPolicy server per second