Skip to content

Commit 5269f03

Browse files
Apply suggestions from code review
Co-authored-by: marciocloudflare <[email protected]>
1 parent c1354c6 commit 5269f03

File tree

1 file changed

+2
-2
lines changed
  • src/content/docs/log-explorer

1 file changed

+2
-2
lines changed

src/content/docs/log-explorer/faq.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@ Log Explorer billing is based on the volume of logs indexed and stored, measured
4949

5050
## Are logs from attack traffic included in my Log Explorer usage?
5151

52-
Yes. Log Explorer bills based on the total volume of logs ingested and stored, including attack traffic. Since these logs are often critical for investigating security incidents, they are treated the same as all other log data.
52+
Yes. Log Explorer bills are based on the total volume of logs ingested and stored, including attack traffic. Since these logs are often critical for investigating security incidents, they are treated the same as all other log data.
5353

54-
## How does Log Explorer store data in R2, and why do not I see it in my own R2 bucket?
54+
## How does Log Explorer store data in R2, and why do I not see it in my own R2 bucket?
5555

5656
Log Explorer uses Cloudflare Logpush and R2 behind the scenes to stream and store logs. For technical and performance reasons, the data is stored in internal, customer-specific R2 buckets managed by Cloudflare. These buckets are single-tenant to keep your data isolated, but they are not visible in your account's R2 interface. You are not billed separately for this storage — it is included in your Log Explorer usage.

0 commit comments

Comments
 (0)