Small lb tickets (#1746)

* Updates to address PCX-1703 and PCX-1929

* Two small wording tweaks

* Updated properties

* Updated with Pedro's feedback

Author: kodster28

products/load-balancing/src/content/load-balancing-analytics/index.md

@@ -30,13 +30,23 @@ These metrics show the number of requests routed to specific pools within a load
 
 Add additional filters for specific pools, times, regions, and origins.
 
-### Latency and Logs
+<Aside type="note">
+
+Load balancing <strong>requests</strong> are the number of uncached requests made by your load balancer. By default, Cloudflare caches resolved IP addresses for up to five seconds.
+
+</Aside>
 
-To view latency and log information for your load balancer, go to **Traffic** > **Load Balancing Analytics** > **Latency**.
+### Latency
 
 **Latency** metrics show an interactive map, helping you identify regions with **Unhealthy** or **Slow** pools.
 
-**Logs** provide a history of all origin server status changes and how they affect your load balancing pools.
+To view latency information for your load balancer, go to **Traffic** > **Load Balancing Analytics** > **Latency**.
+
+### Logs
+
+**Logs** provide a history of all origin server status changes and how they affect your load balancing pools. Load Balancing only logs events that represent a status change for an origin, from healthy to unhealthy or vice versa.
+
+To access logs in the dashboard, go to **Traffic** > **Load Balancing Analytics**. You can also access healthcheck logs [using the API](https://api.cloudflare.com/#load-balancer-healthcheck-events-list-healthcheck-events).
 
 ## GraphQL Analytics
 
@@ -113,7 +123,7 @@ header: Response (truncated)
 <summary>Requests per data center</summary>
 <div>
 
-This query shows the weighted, round-trip time measurement (`avgRttMs`) for individual requets from a specific data center (for example, Singapore or `SIN`) to each pool in a specific load balancer.
+This query shows the weighted, round-trip time measurement (`avgRttMs`) for individual requests from a specific data center (for example, Singapore or `SIN`) to each pool in a specific load balancer.
 
 ```graphql
 ---

products/load-balancing/src/content/understand-basics/load-balancing-logs.md

@@ -15,10 +15,11 @@ Health checks that result in a status change for an origin server are recorded a
 
 ## Important notes
 
-- **Availability monitoring checks the health of origin servers every 15 seconds**. It reports results via email notifications and the Cloudflare API.
+- **Availability monitoring checks the health of origin servers at the specified interval**. It reports results via email notifications and the Cloudflare API. Shorter intervals will improve failover time, but may increase the load on your origin servers.
 - **The default retry rate is 5 retries/second** and is completely configurable. We do not recommend increasing the retry rate significantly. Retries use exponential backoff (1, 2, 4, 8, 16 seconds by default).
-- **You can configure** **monitoring for specific URLs** by sending periodic HTTP requests to the load balancer, taking advantage of customizable intervals, timeouts, and status codes. Once an origin server is marked unhealthy, multi-region failover reroutes traffic to the next available server in failover order.
+- **You can configure monitoring for specific URLs** by sending periodic HTTP requests to the load balancer, taking advantage of customizable intervals, timeouts, and status codes. Once an origin server is marked unhealthy, multi-region failover reroutes traffic to the next available server in failover order.
 - **Load Balancing monitors use the following HTTP user-agent**: `"Mozilla/5.0 (compatible; Cloudflare-Traffic-Manager/1.0; +https://www.cloudflare.com/traffic-manager/; pool-id: $poolid)"`. The `$poolid` contains the first 16 characters of the Load Balancing pool that is the target of the health check.
+- **To increase confidence in pool status**, increase the `consecutive_up` and `consecutive_down` fields when [creating a monitor with the API](https://api.cloudflare.com/#account-load-balancer-monitors-create-monitor). To become healthy or unhealthy, monitored origins must pass this health check the consecutive number of times specified in these parameters.
 - **To prevent health checks from failing**, and to secure user infrastructure against spoofed checks from bad actors, we recommend the following:
   - Only accept connections to hosts listed in the [Cloudflare IP ranges](https://www.cloudflare.com/ips/) in your firewall or web-server.
   - Use Cloudflare's user agent (see above) to reject HTTP requests that don't come from these ranges.
@@ -258,6 +259,30 @@ The sub-string must appear within the first 10KiB of your response body.
           </ul>
         </td>
       </tr>
+      <tr>
+        <td><strong><Code>consecutive_up</Code></strong><br/><Type>integer</Type></td>
+        <td>
+          <p>To be marked healthy, the monitored origin must pass this health check <Code>consecutive_up</Code> consecutive times.</p>
+          <div><Code>2</Code></div>
+        </td>
+        <td>
+          <ul>
+            <li>default value: 1</li>
+          </ul>
+        </td>
+      </tr>
+      <tr>
+        <td><strong><Code>consecutive_down</Code></strong><br/><Type>integer</Type></td>
+        <td>
+          <p>To be marked unhealthy, the monitored origin must pass this health check <Code>consecutive_down</Code> consecutive times.</p>
+          <div><Code>2</Code></div>
+        </td>
+        <td>
+          <ul>
+            <li>default value: 1</li>
+          </ul>
+        </td>
+      </tr>
     </tbody>
   </table>
 </TableWrap>
@@ -304,7 +329,7 @@ For a list of origins that override a monitor's `Host` header:
 
 ## Managing monitors via the Load Balancing dashboard
 
-Use the **Create Load Balancer** or **Edit Load Balancer** panels in the Load Balancing dashboard to manage health check monitors. For step-by-step guidance, see _[Create, attach, and configuring health checks](/create-load-balancer-ui#create-attach-and-configure-health-checks)_.
+Use the **Create Load Balancer** or **Edit Load Balancer** panels in the Load Balancing dashboard to manage health check monitors. For step-by-step guidance, see _[Create, attach, and configuring monitors](/create-load-balancer-ui#3-create-attach-and-configure-monitors)_.
 
 ---
 

products/load-balancing/src/content/understand-basics/monitors.md

@@ -25,6 +25,8 @@ When working with pools, note the following:
 
 **Geo Steering directs traffic to pools based on the client’s region or point of presence.** If there is no Geo Steering configuration for a region or pool, the load balancer will use pool order to determine failover priority.
 
+**If Health Check Regions for a pool is set to All Data Centers (Enterprise)**, pool health is determined by a majority of data centers.
+
 ---
 
 ## Properties