Basic Control Segment

Step 1. Click the Create Segment Button

Click the Create Segment button on the right sidebar, and the following screen will appear.
Please enter the information according to the description below and create the segment.

Step 2. Access Mode Setting

Allow or fundamentally block traffic for actions and URLs where NetFUNNEL is applied.

Step 3. Basic Settings

• Segment Name: Please enter a name that can distinguish between different segments.
• Waiting Room: Choose either the default waiting room or a pre-set waiting room. 🔎 How to Set Up Waiting Rooms
• Responsible Officer: You can designate a person responsible for the segment. Invite a member and assign them as the officer. However, member invitation is supported from the Enterprise plan only.

Step 4. Entry Settings

• EUM URL: Insert the URL you want to collect data and gain insights through EUM. Typically, insert the Main URL to collect information. Including the protocol (ex. https://) is mandatory.
• Allowed Entries: The number of customers that can simultaneously access the page. It is recommended to set it to about 50% of the maximum capacity considering server capacity.
  • Fixed: Control the allowed entries with a fixed value.
  • Dynamic: NetFUNNEL dynamically adjusts the allowed entries between set minimum and maximum values based on server conditions.

Step 5. Set and Test Trigger Rules

Trigger rules can only be used if a separate Dynamic Agent is installed. You can control the influx with various types of rules rather than a fixed method on the page you want to control.

After setting, click Test Trigger Rules to check if it is working properly.

📝 Trigger Rule Settings Description

Logical Operator: Used when adding logical conditions.

• AND: Both the antecedent and subsequent conditions must be satisfied
• OR: Either the antecedent or subsequent condition must be satisfied

Validator: Determines the highest range where the Trigger Rule will be applied based on the set values. You can specify a website or application URL in the Validator to ensure the rules only operate within that range.

Component: Sets the criteria for judgment under the Validator. A total of three criteria are provided: URL, Domain, Path.

Negate: Sets the conditional statement that determines the relationship between Component, Match, and Value (Does/Does not). In the picture below, it is set to ‘does’, which sets the condition to 'if the URL contains the Value'.

Match: Determines the method of applying the rule. Based on Negate = does, each item is as follows (interpreted oppositely if set to does not):

• Equals = if it matches
• Contains = if it contains
• Startwith = if it starts with
• Endwith = if it ends with
• Exists = if it exists

Value: Specifies the specific value that is the comparison target when applying the rule. It determines in which cases the rule is activated. The Value can be a single word or the entire URL, depending on the user's need.

Aa: Decides whether to distinguish between uppercase and lowercase in Value when matching the previously set conditions. For example, if this value is activated, 'Sand' and 'sand' will be recognized as different values.

• You can change the priority of conditions using the right arrow button.
• Up to three logical conditions can be created.

🚩 Trigger Rule Test Results

Once the trigger condition setting is complete, you can check if the condition is working properly.
Below is an example of the trigger rule test.

🙆 If the test is successful

If the condition is set to include the value 'stclab' in the Domain and the test target is http://cloud.stclab.com, the trigger rule matches.

🙅 If the test fails
On the other hand, if the test target is http://cloud.stclabb.com under the same condition, it fails to match the trigger rule.

Step 6. Advanced Settings

You can modify the minimum and maximum values for the re-request period and timeout. Between the set minimum and maximum values, the NetFUNNEL server dynamically operates the re-request period and timeout.

• Re-request Period: Sets the period for the agent to request NetFUNNEL server about the possibility of entry. A higher request period means less frequent inquiries, thus reducing server load and allowing for stable handling of many requests.
• Timeout: NetFUNNEL returns the waiting ticket to the server upon completion of the wait. In exceptional cases where the ticket is not returned, setting a 'timeout' allows the server to retrieve the ticket according to the set period.

Step 7. Segment Creation Completion

Press the Confirm button to complete the creation of the segment.