anchor.diff:        </tr><tr>
           <td><pre>
           SKIP_SSL_VALIDATION: TRUE-OR-FALSE</pre></td>
  -        <td>Set this value to <code>true</code> to allow insecure connections to the UAA and the traffic controller. To block insecure connections to the UAA and traffic controller,
  -        set this value to <code>false</code>.</td>
  +        <td>Set this value to <code>TRUE</code> to allow insecure connections to the UAA and the traffic controller. To block insecure connections to the UAA and traffic controller,
  +        set this value to <code>FALSE</code>.</td>
         </tr><tr>
           <td><pre>
           LOG_LEVEL: INFO</pre></td>
  
positive.code:     with `uaac member add doppler.firehose USERNAME`:
        <pre class="terminal">$ uaac member add doppler.firehose firehose-user</pre>
  
  1. Download the OMS Log Analytics Firehose Nozzle BOSH release from [Github](https://github.com/Azure/oms-log-analytics-firehose-nozzle).
  
      1. Clone the OMS Log Analytics Firehose Nozzle repository:
         <pre class="terminal">
  
negative.code: 
  ## <a id='oms-portal'></a> Step 3: View Logs in OMS Portal
  
  Import the Cloud Foundry OMS view to your OMS Portal to view visualized logs and metrics. You can also create alert rules for specific events.
  
  <p class="note"><strong>Note</strong>: The OMS view of Cloud Foundry is not yet available in the OMS Solutions Gallery. You can add it manually to view your logs in OMS Portal.</p>
  
  ### <a id='import-view'></a> Import the OMS View
  
  1. From the main OMS Overview page, navigate to **View Designer**.
  1. Click **Import**.
  1. Click **Browse**.
  1. Select the **Cloud Foundry (Preview).omsview** file.
  1. Save the view. The main OMS Overview page displays the **Tile**.
  1. Click the **Tile** to view visualized metrics.
  
  See the [OMS Log Analytics View Designer documentation](https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-view-designer) for more information.
  
  ### <a id='alert'></a> Create Alert Rules
  
  See [Understanding alerts in Log Analytics](https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-alerts) for more information about OMS Log Analytics alerts.
  
  ### <a id='queries'></a> Set Alert Queries
  
  This section includes example queries that operators can set in the OMS Portal.
  
  * The following query alerts the operator when the nozzle sends a `slowConsumerAlert` to OMS:
  
      ```
      Type=CF_ValueMetric_CL Name_s=slowConsumerAlert
      ```
  
  * The following query alerts the operator when Loggregator sends an `LGR` to indicate problems with the logging process:
  
      ```
      Type=CF_LogMessage_CL SourceType_s=LGR MessageType_s=ERR
      ```
  
  * The following query alerts the operator when the number of lost events reaches a certain threshold, specified in the OMS Portal:
  
      ```
      Type=CF_CounterEvent_CL Job_s=nozzle Name_s=eventsLost
      ```
  
  * The following query alerts the operator when the nozzle receives the `TruncatingBuffer.DroppedMessages` **CounterEvent**:
  
      ```
      Type=CF_CounterEvent_CL Name_s="TruncatingBuffer.DroppedMessages"
      ```
  
  ## <a id='additional-logging'></a> (Optional) Step 4: Configure Additional Logging
  
  OMS Log Analytics Firehose Nozzle forwards metrics from the Loggregator Firehose to OMS with minimal processing,
  but the nozzle can push additional metrics to OMS.
  
  ### <a id='events'></a> Log Sent, Received, and Lost Events
  
  If you set the `LOG_EVENT_COUNT` environment variable to `TRUE` in the [manifest](#deploy), the nozzle periodically sends
  the count of sent, received, and lost events to OMS. The value you set for the `LOG_EVENT_COUNT_INTERVAL` determines how
  frequently the nozzle sends the count.
  
  <p class="note"><strong>Note</strong>: The nozzle does not count <strong>CounterEvents</strong> themselves in the sent, received, or lost event count.</p>
  
  The nozzle sends the count as a **CounterEvent** with a **CounterKey** of one of the following:
  
  <table>
    <tr>
      <th>CounterEvent</th>
      <th>CounterKey</th>
    </tr><tr>
      <td><code>nozzle.stats.eventsReceived</td>
      <td>The number of events the Firehose has received during the interval</td>
    </tr><tr>
      <td><code>nozzle.stats.eventsSent</code></td>
      <td>The number of events the nozzle has successfully sent to OMS during the interval</td>
    </tr><tr>
      <td><code>nozzle.stats.eventsLost</code></td>
      <td>The number of events the nozzle has tried to send to OMS during the interval, but failed to send after 4 attempts</td>
    </tr>
  </table>
  
  In most cases, the total count of `eventsSent` plus `eventsLost` is less than the total `eventsReceived` at the same time.
  The nozzle buffers some messages and posts them in a batch to OMS. Operators can adjust the buffer size by adjusting
  the `OMS_BATCH_TIME` and `OMS_MAX_MSG_NUM_PER_BATCH` environment variables in the [manifest](#deploy).
  
  ### <a id='slow-consumer'></a> Log Slow Consumer Alerts
  
  <p class="note"><strong>Note</strong>: The nozzle does not count <strong>ValueMetrics</strong> in the sent, received, or lost event count.</p>
  
  Loggregator sends the nozzle a `slowConsumerAlert` in the following situations:
  
  * WebSocket sends the error code `ClosePolicyViolation (1008)`
  * The nozzle receives a **CounterEvent** with the value `TruncatingBuffer.DroppedMessages`
  
  In either case, the nozzle sends the `slowConsumerAlert` event to OMS as the following **ValueMetric**:
  
  <table>
    <tr>
      <th>ValueMetric</th>
      <th>MetricKey</th>
    </tr><tr>
      <td><code>nozzle.alert.slowConsumerAlert</code></td>
      <td>1</td>
    </tr>
  </table>
  
  See the _Slow Nozzle Alerts_ section of the [Loggregator Guide for Cloud Foundry Operators](../../loggregator/log-ops-guide.html#slow-noz) for more information.
  
  ## <a id='scaling'></a> (Optional) Step 5: Scale the Deployment
  
  ### <a id='scale-nozzle'></a> Scale the Nozzle
  
  If the nozzle is unable to keep up with processing logs from the Firehose, Loggregator alerts the nozzle.
  When the nozzle receives the alert, it sends a `slowConsumerAlert` to OMS. If this happens, scaling up the nozzle minimizes data loss.
  
  If an operator chooses to scale up their deployment, the Firehose evenly distributes events across all instances of the nozzle.
  See the _Scaling Nozzles_ section of the [Loggregator Guide for Cloud Foundry Operators](../../loggregator/log-ops-guide.html#scaling-nozzles) for more information.
  
  Operators can [create an alert rule](#alert) for the `slowConsumerAlert` message.
  
  ### <a id='scale-loggregator'></a> Scale Loggregator
  
  Loggregator sends `LGR` log messages to indicate problems with the logging process.
  See the _Scaling Loggregator_ section of the [Loggregator Guide for Cloud Foundry Operators](../../loggregator/log-ops-guide.html#scaling) for more information.
  
  Operators can [create an alert rule](#alert) for the `LGR` message.
  