Which profile types are there; which vService types can they be used with?

Short answer

In the Configuration Menu, there are 10 profile types in the Profiles (L4-L7 Behavior Sets) group under Load Balancer: Health Checks, Compression, Cache, Trusted Proxies, Logs, Timeouts, vService Limits, Notifications, Reports and Content Pages. TLS behavior is additionally determined with the TLS Security Profiles under Certificates & PKI. Cache, Compression and Trusted Proxies are selected only on an HTTP vService; Logs, Timeouts, vService Limits, Notifications and TLS Security Profiles are selected on HTTP and L7 TCP vServices. Reports breakdowns are produced only on an HTTP vService; on an L7 TCP vService, the report consists only of time series charts. Health Checks are bound not to the vService but to the Backend Service or Backend Group, and Content Pages to actions and security profiles.

How Does It Work?

1. A profile is defined once on the related screen in the Configuration Menu → Load Balancer → Profiles (L4-L7 Behavior Sets) group (Configuration Menu · Load Balancer).
2. In the Details panel of the vService form, the related box is checked and the profile is selected; Health Checks, on the other hand, are selected in the Backend Service or Backend Group form.
3. A profile is a shared record: a change made in a profile is applied at the same time to all the vServices and Backend Services that use it (What is a Profile, and why is it defined as a separate object?).
4. In a cluster setup, a profile change is transferred to the peer device immediately with the default automatic synchronization; if Manual Sync Mode is on, it stays only on the device where the change was made until it is sent with Synchronize.

Profiles and vService Types

Profile	HTTP	L7 TCP	Network	Where it is bound
Health Checks	✓	✓	✓ (TCP - L4 and UDP - L4)	Backend Service or Backend Group → Health Check
Compression	✓	-	-	vService → Details → Compression
Cache	✓	-	-	vService → Details → Cache
Trusted Proxies	✓	-	-	vService → Details → Trusted Proxy
Logs	✓	✓	-	vService → Details → LOG
Timeouts	✓	✓	-	vService → Details → Timeout
vService Limits	✓	✓	-	vService → Details → vService Limits
Notifications	✓	✓	-	vService → Details → Notification
Reports	✓	Selected; the report consists only of time series charts, breakdowns are not produced	Listed in the selector, the profile is not saved; the Report tab does not open	vService → Details → Report
Content Pages	✓	-	-	Actions such as Show content, Bot/DDoS, WAF and AGS profiles
TLS Security Profiles	✓	✓	-	vService → Details → SSL Security

• The Details panel of a Network vService contains only Report and LB Algorithm; distribution is determined by the algorithm and the health check result of the Backend Services. On a Network vService, the health check result is not taken into account with the ANY - L3 protocol and while Port Range is on (vService · Network (packet level)).
• The SSL Security box appears only if a protocol that terminates TLS is selected in at least one frontend row (What is a TLS Security Profile, and what does it configure?).
• General comparison of the types: What are the feature differences between HTTP, L7 TCP and Network vServices?

Profiles in TR7

Profiles are defined in the Configuration Menu and selected from the vService form; it is also possible to create a new profile without leaving the form (Can I create a new action, health check or SSL profile without leaving the vService form?). The vServices in which a profile is used are seen from the Used in tab in the profile preview (How do I understand the impact of changing a profile before I change it ("Used in")?). When no profile is selected for Timeouts and vService Limits, the built-in default values apply (Timeouts · The Default Timeouts Profile Behavior).

Common Misconceptions

• "A health check is assigned to the vService." A Health Checks profile is assigned to the Backend Service or Backend Group; all the vServices that use the same Backend Service see the same result.
• "When a Reports profile is selected on an L7 TCP or Network vService, a full report comes as on HTTP." Breakdowns are produced only on an HTTP vService; on L7 TCP, the report consists only of time series charts, and on a Network vService the profile is not saved (Why can't I see the Report tab?).
• "If no profile is selected, no timeout or limit is applied." Even if no profile is selected for Timeouts and vService Limits, the built-in default values apply (Is it right to use the default profiles as they are in production?).
• "The SSL Security box has disappeared." If TLS is not terminated in any frontend row, the box is hidden.

How it is done in the documentation

• Profiles · Profiles
• vService · Feature / Capability Comparison
• Reports · Supported vService Types
• Content Pages · Usage Locations

Related questions

• What is a Profile, and why is it defined as a separate object?
• Is it right to use the default profiles as they are in production?
• How do I understand the impact of changing a profile before I change it ("Used in")?