Small changes to 2 analytics docs (#21269)

* Small changes to 2 analytics docs

* remove package-lock changes

---------

Co-authored-by: kodster28 <[email protected]>

Author: rianvdm

src/content/docs/analytics/graphql-api/sampling.mdx

@@ -6,6 +6,8 @@ sidebar:
 
 ---
 
+For a deep-dive on how sampling at Cloudflare works, see [Understanding sampling in Cloudflare Analytics](/analytics/sampling/).
+
 ## Overview
 
 In a small number of cases, the analytics provided on the Cloudflare dashboard and GraphQL Analytics API are based on a **sample** — a subset of the dataset. In these cases, Cloudflare Analytics returns an estimate derived from the sampled value. For example, suppose that during an attack the sampling rate is 10% and 5,000 events are sampled. Cloudflare will estimate 50,000 total events (5,000 × 10) and report this value in Analytics.

src/content/docs/logs/about.mdx

@@ -12,6 +12,10 @@ Logpush delivers logs in batches as quickly as possible, with no minimum batch s
 
 Logpush does not offer storage or search functionality for logs; its primary aim is to send logs as quickly as they arrive.
 
+## Limits
+
+There is currently a max limit of **4 Logpush jobs per zone**. Trying to create a job once the limit has been reached will result in an error message: `creating a new job is not allowed: exceeded max jobs allowed`.
+
 ## Availability
 
 <FeatureTable id="analytics.logpush" />