[MNM] VPC flow logs #21548
[MNM] VPC flow logs #21548
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryIntroduced VPC flow logs feature for Magic Network Monitoring, enhancing cloud traffic visibility.
Modified Files
Added Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
|
|
||
| ### 1. Verify cloud flow log capabilities | ||
|
|
||
| Verify that your AWS account is capable of exporting AWS VPC flow logs via AWS Firehose. Today, Magic Network Monitoring only supports VPC flow log ingestion for AWS. |
There was a problem hiding this comment.
Nit: Maybe "Currently, " instead of "Today, "?
|
|
||
| Customers using Magic Network Monitoring can export virtual private cloud (VPC) flow logs from their cloud environment to Cloudflare's network. Cloudflare will then process these VPC flow logs and display analytics on your cloud traffic in the dashboard. Customers can also ingest data on their cloud traffic via our public GraphQL API which powers the cloud traffic analytics in the dashboard. | ||
|
|
||
| Today, Magic Network Monitoring only supports AWS VPC flow logs via AWS Firehose. AWS VPC flow logs can only be configured via Cloudflare's API for Magic Network Monitoring. |
There was a problem hiding this comment.
Nit: Maybe "Currently, " instead of "Today, "?
Co-authored-by: Pedro Sousa <[email protected]>
* added flow logs page * changed page weight * added content * added netflow section * added flow log * added link * corrected headers * refined text * added beta badge * refined text * added apirequest * refined steps * Apply suggestions from code review Co-authored-by: Pedro Sousa <[email protected]> * added suggestion --------- Co-authored-by: Pedro Sousa <[email protected]>
2 participants
Summary
Closes PCX-15353
Documentation checklist