Controller Configuration

The AppSentinels Controller can be configured to filter out specific types of API traffic that do not require monitoring—such as static files or health check endpoints. This filtering helps optimize performance and reduce the volume of data sent from the controller to the AppSentinels API Security Platform.

Purpose of Filtering

• Exclude Static Resources: Skip monitoring of APIs serving static content like images, CSS, JavaScript, and fonts.
• Ignore Health Endpoints: Prevent health check endpoints (e.g., /dp-health, /health) from being forwarded.
• Control Data Volume: Ensure only relevant traffic is analyzed, keeping system resource usage efficient.

How It Works

The filtering is based on regular expressions defined in the controller configuration. You can configure URI patterns and headers to be bypassed.

Example snippet:

{
  "ingress_filter": {
    "uribypass": {
      "regex-1": "[^\\s]+(.*?)\\.(dp-health|txt|png|PNG|jpg|jpeg|io|tff|woff|woff2|ico|css|pdf|html|mp4|php|ajax|js|tiff|ttf|docx|svg|wasm|aspx|json|xml|dp-health|health)[/]?$"
    },
    "headerbypass": {}
  }
}

This regex tells the controller to bypass traffic matching static file types or common health check URIs.

Configuration Path

To modify the controller settings, navigate to Settings → Controller Configuration
Here you can add or update URI and header bypass filters as per your application’s needs.