Skip to content

Commit b4e66c4

Browse files
authored
Dashbutton updates (#24998)
* Dashbutton updates * Removed DashButton component due to routes missing.
1 parent 8810f50 commit b4e66c4

File tree

14 files changed

+117
-72
lines changed

14 files changed

+117
-72
lines changed

src/content/docs/magic-network-monitoring/get-started.mdx

Lines changed: 13 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 2
66
---
77

8-
import { APIRequest, Badge, GlossaryTooltip } from "~/components";
8+
import { APIRequest, Badge, GlossaryTooltip, DashButton } from "~/components";
99

1010
Magic Network Monitoring includes an onboarding workflow that guides you step-by-step through the product configuration process. If you are unable to complete the configuration in one session, you can exit the workflow and resume it at any time.
1111

@@ -28,13 +28,15 @@ Refer to [Supported routers](/magic-network-monitoring/routers/supported-routers
2828

2929
When you register your router with Cloudflare, your router links your NetFlow or sFlow data to your Cloudflare account.
3030

31-
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
32-
2. Go to **Analytics & Logs** > **Magic Monitoring**.
33-
3. In **Magic Network Monitoring Analytics**, select **Configure Magic Network Monitoring**.
34-
4. Select the **Configure routers** tab.
35-
5. (Optional) Under **IP Address**, enter your router's public IP address.
36-
6. Under **Default router sampling rate**, enter a value for the <GlossaryTooltip term="sampling">sampling</GlossaryTooltip> rate. The value should match the sampling rate of your NetFlow or sFlow configuration.
37-
7. Select **Next**.
31+
1. In the Cloudflare dashboard, go to the **Magic Monitoring** page.
32+
33+
<DashButton url="/?to=/:account/network-monitoring" />
34+
35+
2. In **Magic Network Monitoring Analytics**, select **Configure Magic Network Monitoring**.
36+
3. Select the **Configure routers** tab.
37+
4. (Optional) Under **IP Address**, enter your router's public IP address.
38+
5. Under **Default router sampling rate**, enter a value for the <GlossaryTooltip term="sampling">sampling</GlossaryTooltip> rate. The value should match the sampling rate of your NetFlow or sFlow configuration.
39+
6. Select **Next**.
3840

3941
### 3. Configure your router
4042

@@ -94,7 +96,8 @@ AWS VPC flow logs can only be configured via the Cloudflare API for Magic Networ
9496

9597
After setting up AWS Firehose to send VPC flow logs to Magic Network Monitoring, you can confirm that Cloudflare is receiving the logs as expected by searching for your cloud traffic data in the analytics page of the Magic Network Monitoring dashboard.
9698

97-
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
98-
2. Go to **Analytics & Logs** > **Magic Monitoring**.
99+
1. In the Cloudflare dashboard, go to the **Magic Monitoring** page.
100+
101+
<DashButton url="/?to=/:account/network-monitoring" />
99102

100103
The default view will be the analytics dashboard for Magic Network Monitoring.

src/content/docs/magic-network-monitoring/index.mdx

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,14 +9,7 @@ head:
99
---
1010

1111
import {
12-
CardGrid,
13-
Description,
14-
Feature,
15-
GlossaryTooltip,
16-
LinkTitleCard,
17-
Plan,
18-
RelatedProduct,
19-
} from "~/components";
12+
CardGrid, Description, Feature, GlossaryTooltip, LinkTitleCard, Plan, RelatedProduct, DashButton } from "~/components";
2013

2114
<Description>
2215

@@ -28,7 +21,9 @@ Improve your network and cloud traffic visibility. Customers with public IPs can
2821

2922
Magic Network Monitoring provides visibility into your network traffic and cloud traffic by analyzing network <GlossaryTooltip term="flow data">flow data</GlossaryTooltip> sent from a customer's routers or cloud environment. Magic Network Monitoring supports NetFlow v5, NetFlow v9, IPFIX, and sFlow. In cloud environments, Magic Network Monitoring supports AWS VPC flow logs via AWS Firehose.
3023

31-
Magic Network Monitoring is generally available to everyone with a Cloudflare account by default. You can log in to your Cloudflare dashboard, select your account, then go to **Analytics & Logs** > **Magic Monitoring** to get started.
24+
Magic Network Monitoring is generally available to everyone with a Cloudflare account by default. You can log in to your Cloudflare dashboard, select your account, then go to the **Magic Monitoring** page to get started.
25+
26+
<DashButton url="/?to=/:account/network-monitoring" />
3227

3328
Everyone can use the [free version](/magic-network-monitoring/magic-network-monitoring-free/) of Magic Network Monitoring in a home network, network lab, or business to get end to end visibility across their network traffic. Potential enterprise customers are encouraged to use the free version to run a proof of concept.
3429

src/content/docs/magic-network-monitoring/magic-network-monitoring-free.mdx

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ head:
88
content: Magic Network Monitoring free version
99
---
1010

11+
import { DashButton } from "~/components";
12+
1113
The free version of Magic Network Monitoring (MNM) is generally available to everyone with a Cloudflare account by default.
1214

1315
All free customers are encouraged to join [Cloudflare's Discord server](https://discord.com/invite/cloudflaredev) to discuss the use cases, configuration, and troubleshooting of Magic Network Monitoring. Free customers are always welcome to provide product feedback and discuss feature requests. The product and engineering team that works on Magic Network Monitoring regularly engages with the Discord community.
@@ -18,9 +20,11 @@ You can find the channel by joining the Cloudflare Developers Discord server. Th
1820

1921
The free version includes all the features of the enterprise version, but has network flow volume and configuration limitations. These limits are detailed below.
2022

21-
1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
22-
2. Go to **Analytics & Logs** > **Magic Monitoring**.
23-
3. Complete the onboarding wizard to configure Magic Network Monitoring. Refer to [Get started](/magic-network-monitoring/get-started/) for more information.
23+
1. In the Cloudflare dashboard, go to the **Magic Monitoring** page.
24+
25+
<DashButton url="/?to=/:account/network-monitoring" />
26+
27+
2. Complete the onboarding wizard to configure Magic Network Monitoring. Refer to [Get started](/magic-network-monitoring/get-started/) for more information.
2428

2529
## Limitations
2630

src/content/docs/magic-network-monitoring/rules/index.mdx

Lines changed: 23 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66
order: 4
77

88
---
9-
import { Render } from "~/components"
9+
import { Render, DashButton } from "~/components"
1010

1111
Magic Network Monitoring rules allow you to monitor your network traffic for DDoS attacks on specific IP addresses or IP prefixes within your network. If the network traffic that is monitored by a rule exceeds the rule's threshold or contains a DDoS attack fingerprint, then you will receive an alert.
1212

@@ -36,28 +36,34 @@ Refer to [Account name](/fundamentals/account/create-account/#account-name) to l
3636

3737
To create a new rule:
3838

39-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
40-
2. Go to **Analytics & Logs** > **Magic Monitoring**.
41-
3. Select **Configure Magic Network Monitoring** > **Add new rule**.
42-
4. Create a new static traffic threshold rule according to your needs. Refer to the documentation on [static threshold](/magic-network-monitoring/rules/static-threshold/) rules for more information on each field in the static threshold rule's configuration.
43-
5. Select **Create a new rule** when you are finished.
39+
1. In the Cloudflare dashboard, go to the **Magic Monitoring** page.
40+
41+
<DashButton url="/?to=/:account/network-monitoring" />
42+
43+
2. Select **Configure Magic Network Monitoring** > **Add new rule**.
44+
3. Create a new static traffic threshold rule according to your needs. Refer to the documentation on [static threshold](/magic-network-monitoring/rules/static-threshold/) rules for more information on each field in the static threshold rule's configuration.
45+
4. Select **Create a new rule** when you are finished.
4446

4547
## Edit rules in the dashboard
4648

47-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
48-
2. Go to **Analytics & Logs** > **Magic Monitoring**.
49-
3. Select **Configure Magic Network Monitoring**.
50-
4. Find the static threshold rule you want to edit, and select **Edit**.
51-
5. Edit the appropriate fields. Refer to [Rule configuration fields](/magic-network-monitoring/rules/static-threshold/#rule-configuration-fields) for more information on what each field does.
52-
6. Select **Save** when you are finished.
49+
1. In the Cloudflare dashboard, go to the **Magic Monitoring** page.
50+
51+
<DashButton url="/?to=/:account/network-monitoring" />
52+
53+
2. Select **Configure Magic Network Monitoring**.
54+
3. Find the static threshold rule you want to edit, and select **Edit**.
55+
4. Edit the appropriate fields. Refer to [Rule configuration fields](/magic-network-monitoring/rules/static-threshold/#rule-configuration-fields) for more information on what each field does.
56+
5. Select **Save** when you are finished.
5357

5458
## Delete rules in the dashboard
5559

56-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
57-
2. Go to **Analytics & Logs** > **Magic Monitoring**.
58-
3. Select **Configure Magic Network Monitoring**.
59-
4. Find the static threshold rule you want to delete, and select **Delete**.
60-
5. Select **I understand that deleting a rule is permanent**, and select **Delete** again.
60+
1. In the Cloudflare dashboard, go to the **Magic Monitoring** page.
61+
62+
<DashButton url="/?to=/:account/network-monitoring" />
63+
64+
2. Select **Configure Magic Network Monitoring**.
65+
3. Find the static threshold rule you want to delete, and select **Delete**.
66+
4. Select **I understand that deleting a rule is permanent**, and select **Delete** again.
6167

6268
## Common settings that apply to all rule types
6369

src/content/docs/magic-network-monitoring/rules/rule-notifications.mdx

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ pcx_content_type: how-to
44
sidebar:
55
order: 4
66
---
7-
import { Render } from "~/components"
7+
import { Render, DashButton } from "~/components"
88

99
After configuring one or multiple rule types in Magic Network Monitoring, customers can also choose to receive notifications via email, webhook, or PagerDuty when a rule is triggered.
1010

@@ -35,8 +35,11 @@ You can read [Cloudflare's Notifications documentation](/notifications/) for mor
3535

3636
To configure static threshold notifications:
3737

38-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
39-
2. Go to **Notifications** > **Add**.
38+
1. In the Cloudflare dash, go to the **Notifications** page.
39+
40+
<DashButton url="/?to=/:account/notifications" />
41+
42+
2. Select **Add**.
4043
3. Select **Magic Transit** from the product dropdown menu.
4144
4. Find the **Magic Network Monitoring: Volumetric Attack** alert, and select **Select**.
4245
5. Fill in the notification configuration details.
@@ -46,8 +49,11 @@ To configure static threshold notifications:
4649

4750
To configure dynamic threshold notifications:
4851

49-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
50-
2. Go to **Notifications** > **Add**.
52+
1. In the Cloudflare dash, go to the **Notifications** page.
53+
54+
<DashButton url="/?to=/:account/notifications" />
55+
56+
2. Select **Add**.
5157
3. Select **Magic Transit** from the product dropdown menu.
5258
4. Find the **Magic Network Monitoring: Volumetric Attack** alert, and select **Select**.
5359
5. Fill in the notification configuration details.
@@ -57,8 +63,11 @@ To configure dynamic threshold notifications:
5763

5864
To configure sFlow DDoS attack notifications:
5965

60-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
61-
2. Go to **Notifications** > **Add**.
66+
1. In the Cloudflare dash, go to the **Notifications** page.
67+
68+
<DashButton url="/?to=/:account/notifications" />
69+
70+
2. Select **Add**.
6271
3. Select **Magic Transit** from the product dropdown menu.
6372
4. Find the **Magic Network Monitoring: DDoS Attack** alert, and select **Select**.
6473
5. Fill in the notification configuration details.

src/content/docs/magic-network-monitoring/rules/static-threshold.mdx

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ sidebar:
55
order: 1
66
---
77

8+
import { DashButton } from "~/components";
9+
810
A static threshold rule allows you to define a constant numeric threshold, in terms of bits or packets, for DDoS traffic monitoring. The total traffic across all IP prefixes and IP addresses in the rule is compared to the static rule threshold. If the total traffic exceeds the static rule threshold for the duration of the rule, then an alert is sent.
911

1012
Customers that send NetFlow and/or sFlow data to Cloudflare can configure static threshold rules.
@@ -60,10 +62,12 @@ Cloudflare recommends that new customers set a rule threshold that is two times
6062

6163
To find the maximum non-attack traffic for a one minute time interval over the past 14-30 days, you can filter for the specific rule you want to analyze. To do that:
6264

63-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account.
64-
2. Go to **Analytics & Logs** > **Magic Monitoring**.
65-
3. Select **Add filter**.
66-
4. In **New filter**, use the drop-down menus to create the following filter:
65+
1. In the Cloudflare dashboard, go to the **Magic Monitoring** page.
66+
67+
<DashButton url="/?to=/:account/network-monitoring" />
68+
69+
2. Select **Add filter**.
70+
3. In **New filter**, use the drop-down menus to create the following filter:
6771

6872
| Field | Operator | Rule name |
6973
| :---- | :---- | :---- |

src/content/docs/magic-network-monitoring/tutorials/graphql-analytics.mdx

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ head:
1111
content: GraphQL Analytics
1212
---
1313

14-
import { GlossaryTooltip } from "~/components";
14+
import { GlossaryTooltip, DashButton } from "~/components";
1515

1616
Use the GraphQL Analytics API to retrieve Magic Network Monitoring <GlossaryTooltip term="flow data">flow data</GlossaryTooltip>.
1717

@@ -21,7 +21,10 @@ Before you begin, you must have an [API token](/analytics/graphql-api/getting-st
2121

2222
To construct a Magic Network Monitoring GraphQL query for an object, you will need a Cloudflare Account ID.
2323

24-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
24+
1. Log in to the Cloudflare dashboard, and select your account.
25+
26+
<DashButton url="/?to=/:account/home" />
27+
2528
2. The URL in your browser's address bar should show `https://dash.cloudflare.com/` followed by a hex string. The hex string is your Cloudflare Account ID.
2629

2730
## Explore GraphQL schema with Magic Network Monitoring example

src/content/docs/magic-transit/network-health/run-endpoint-health-checks.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ sidebar:
99

1010
---
1111

12-
import { CURL, Render } from '~/components';
12+
import { CURL, Render, DashButton } from '~/components';
1313

1414
Magic Transit uses endpoint health checks to determine the overall health of your [inter-network connections](/magic-transit/reference/gre-ipsec-tunnels/). Probes originate from Cloudflare infrastructure, outside customer network namespaces, and target IP addresses deep within your network, beyond the tunnel-terminating border router. These "long distance" probes are purely diagnostic.
1515

@@ -136,8 +136,11 @@ You can set up alerts to be notified when the state of your endpoint's health is
136136
```
137137

138138
2. Take note of the `id` value for the endpoint you want to get alerts for.
139-
3. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account.
140-
4. Go to **Notifications** > **Add**.
139+
3. In the Cloudflare dash, go to the **Notifications** page.
140+
141+
<DashButton url="/?to=/:account/notifications" />
142+
143+
4. Select **Add**.
141144
5. From the drop down menu, select *Magic Transit*.
142145
6. Select **Magic Endpoint Health Check Alert**.
143146
7. Provide a name for your new notification and optionally provide a description.

src/content/docs/magic-wan/configuration/connector/device-metrics.mdx

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ sidebar:
55
order: 8
66
---
77

8+
import { DashButton } from "~/components";
9+
810
Cloudflare customers can inspect metrics for a specific Magic WAN Connector in the Cloudflare dashboard. The Magic WAN Connector device metrics measured by Cloudflare include:
911

1012
- CPU load
@@ -14,10 +16,12 @@ Cloudflare customers can inspect metrics for a specific Magic WAN Connector in t
1416

1517
To check for Connector metrics:
1618

17-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
18-
2. Go to **Magic WAN** > **Configuration** > **Connectors**.
19-
3. Select the Connector you want to check metrics for.
20-
4. In the side panel that opens, scroll down to **Usage information**.
19+
1. In the Cloudflare dash, go to the **Configuration* page.
20+
21+
<DashButton url="/?to=/:account/magic-wan/configuration" />
22+
23+
2. In the **Connectors** tab, select the Connector you want to check metrics for.
24+
3. In the side panel that opens, scroll down to **Usage information**.
2125

2226
### Query metrics with GraphQL
2327

src/content/docs/magic-wan/configuration/connector/maintenance/deactivate-connector.mdx

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,12 @@ sidebar:
66

77
---
88

9-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
10-
2. Go to **Magic WAN** > **Configuration** > **Connectors**.
11-
3. Find the Connector you want to deactivate, select the three dots next to it > **Edit**.
12-
4. In **Status**, select _Deactivated_ from the dropdown.
13-
5. Select **Update**.
9+
import { DashButton } from '~/components';
10+
11+
1. In the Cloudflare dash, go to the **Configuration* page.
12+
13+
<DashButton url="/?to=/:account/magic-wan/configuration" />
14+
15+
2. In the **Connectors** tab, find the Connector you want to deactivate, select the three dots next to it > **Edit**.
16+
3. In **Status**, select _Deactivated_ from the dropdown.
17+
4. Select **Update**.

0 commit comments

Comments
 (0)