logger

Author: gitName

articles/api-management/api-management-howto-cache.md

@@ -81,7 +81,10 @@ To see the caching in action, call an operation from the portal.
 1. Select the API to which you added caching policies.
 1. Select an operation to test.
 1. Select the **Test** tab in the top right menu.
-1. Select **Send**.
+1. Select **Trace** two or three times in quick succession.
+1. Under **HTTP response**, select the **Trace** tab.
+1. Jump to the **Inbound** section and scroll to the `cache-lookup` policy. You should see a message similar to:
+   ` "Cache lookup resulted in a hit! Cached response will be used. Processing will continue from the step in the response pipeline that is after the corresponding `cache-store`."`
 
 ## Related content
 * For more information about caching policies, see [Caching policies][Caching policies] in the [API Management policy reference][API Management policy reference].

articles/api-management/api-management-log-to-eventhub-sample.md

@@ -45,7 +45,7 @@ An alternative option was to use the `application/http` media type as described
 To be able to create this message, we need to take advantage of C# based [Policy expressions](./api-management-policy-expressions.md) in Azure API Management. Here is the policy, which sends an HTTP request message to Azure Event Hubs.
 
 ```xml
-<log-to-eventhub logger-id="conferencelogger" partition-id="0">
+<log-to-eventhub logger-id="myapilogger" partition-id="0">
 @{
    var requestLine = string.Format("{0} {1} HTTP/1.1\r\n",
                                                context.Request.Method,
@@ -97,7 +97,7 @@ The policy to send the response HTTP message looks similar to the request and so
 <policies>
   <inbound>
       <set-variable name="message-id" value="@(Guid.NewGuid())" />
-      <log-to-eventhub logger-id="conferencelogger" partition-id="0">
+      <log-to-eventhub logger-id="myapilogger" partition-id="0">
       @{
           var requestLine = string.Format("{0} {1} HTTP/1.1\r\n",
                                                       context.Request.Method,
@@ -125,7 +125,7 @@ The policy to send the response HTTP message looks similar to the request and so
       <forward-request follow-redirects="true" />
   </backend>
   <outbound>
-      <log-to-eventhub logger-id="conferencelogger" partition-id="1">
+      <log-to-eventhub logger-id="myapilogger" partition-id="1">
       @{
           var statusLine = string.Format("HTTP/1.1 {0} {1}\r\n",
                                               context.Response.StatusCode,