Introduction to the NetFUNNEL Web Agent

NetFUNNEL supports traffic control without directly interfering with the service environment.

• Service: A target website (URL) that interacts with NetFUNNEL to apply traffic control.

To apply traffic control without interfering with the service infrastructure, connect the agent to a built web environment.

WEB Agent Technical Overview

Once the agent is installed on the service, it is ready to communicate with NetFUNNEL.

NetFUNNEL provides traffic control in the following flow.

NetFunnel Agent Features

The NetFUNNEL Agent monitors URLs within a segment to provide dynamic waiting / blocking rooms without directly interfering with the service.

Once the agent has been successfully installed, the following features are available in the NetFUNNEL console.

Allows Multi-domain

NetFUNNEL allows you to manage the traffic of multiple sites built on your service separately.

• For example, if your service is divided into domains called promotion.com / platform.com / service.com, you can create and manage a project for each main domain.

Dynamic traffic control based on URL

You can control traffic in real time by registering URLs that require traffic control to a segment.

URLs can be controlled by checking whether they match the query parameter.

If the URL of the segment that requires traffic control has a query argument, you must enter the full string to match when registering the URL in the segment.

For example, if you set the main domain to https://test.com/main and the URL to be controlled to https://test.com/main?key=value, you must include the appropriate query argument and register it in the segment.

NetFUNNEL supports traffic control through basic/path control segments.

• Basic control: controls entries to a single page, and allows you to control the maximum number of entries per second for a registered URL.
  • Basic control segment types
    • Static : Controls for a fixed number of entries allowed regardless of processing time.
    • Dynamic : Enter the minimum/maximum number of allowed entries, and automatically adjust the number of allowed entries based on the set baseline segment processing time.
• Path control: Specify the start/end URL and control incoming entries to that segment.

End User Monitoring (EUM)

EUM data is collected from service visitors and an interface is provided for monitoring in the console.

Traffic control is provided regardless of browser type.

Monitoring provides transaction and URL monitoring.

• Learn Transaction Monitoring
• Learn URL Monitoring

EUM data collection is performed using the Beacon API and is supported in the Chrome web browser.
If the service visitor accesses via Internet Explorer (IE version 11.1 or lower), the data is missing.