1. On the Main tab, click System > Logs > Configuration > Log Publishers .
   The Log Publishers screen opens.
2. Click Create.
3. In the Name field, type a unique, identifiable name for this publisher.
4. For the Destinations setting, select a destination from the Available list, and click << to move the destination to the Selected list.
   Note: If you are using a formatted destination, select the destination that matches your log servers, such as Remote Syslog, Splunk, or ArcSight.
5. Click Finished.

1. On the Main tab, click Local Traffic > Virtual Servers .
   The Virtual Server List screen opens.
2. Click the Create button.
   The New Virtual Server screen opens.
3. From the HTTP Profile list, select http.
4. In the Resources area, for the iRules setting, from the Available list, select the name of the QoE iRule that you want to assign, and move the name into the Enabled list.
5. In the Resources area of the screen, from the Default Pool list, select the relevant pool name.
6. Click Finished.
7. On the Main tab, click Local Traffic > Virtual Servers .
   The Virtual Server List screen opens.
8. Click the name of the virtual server you want to modify.
9. From the Configuration list, select Advanced.
10. From the QoE list, select a QoE profile to attach to the virtual server.
11. Click Update to save the changes.

1. On the Main tab, click Policy Enforcement > Policies .
   The Policies screen opens.
2. Click the name of the enforcement policy you want to add rules to.
   The properties screen for the policy opens.
3. In the Policy Rules area, click Add.
   The New Rule screen opens.
4. In the Name field, type a name for the rule.
5. In the Precedence field, type an integer that indicates the precedence for the rule in relation to the other rules. Number 1 has the highest precedence. Rules with higher precedence are evaluated before other rules with lower precedence.
   Tip: All rules in a policy are run concurrently. Precedence takes effect when there are conflicting rules. The conflict occurs when the traffic matches two rules and the policy actions from these rules differ. For example, if you have rule 1 with precedence 10 and Gate Status disabled for a search engine, and you have rule 2 with precedence 11 and Gate Status enabled, then rule 1 is processed first because it has higher precedence. Rules conflict if they have identical or overlapping classification criteria (for the traffic that matches more than one rule). In some cases, different policy actions are not conflicting, and hence, applied in parallel.
6. Use the Classification, URL, Flow, and Custom Criteria tabs to identify the traffic that you want to be affected by this rule.
7. From the QoE Reporting list, select Enabled.
8. In the QoE Destination setting, from the HSL list, select the name of the publisher that specifies the server or pool of remote HSL servers to send the logs and select the format script of the report from the Format Script list.
   Note: If you are using a formatted destination, select the publisher that matches your log servers, such as Remote Syslog, Splunk, or ArcSight.
9. Click Finished.

In an enforcement policy, a rule can send QoE-based information about traffic that matches certain criteria to an external high-speed logging (HSL) server. The logs include the following comma-separated values in the order listed.

  
Apr 30 14:30:14 slot2/sush_vic_172 info tmm[4243]: 23003143,6,1.0.0,1430429414,610,404234567123456,IMSI,10.1.1.11,37112,11.1.1.100,80,6,2426616,0,320x240,FLV,,1,0,5
Apr 30 14:30:46 slot2/sush_vic_172 info tmm[4243]: 23003143,6,1.0.0,1430429446,88,404234567123456,IMSI,10.1.1.11,37113,11.1.1.100,80,6,164771,0,480x320,MP4,,70,0,4