跳转到主要内容

Test your first application

import { DashButton, Render } from "~/components";

You have now set up your Zero Trust organization, configured the Cloudflare One Client, installed it on devices, and created your Access and Gateway policies. The next step is to test those policies.

1. Manually test your policies

Test if the Access or Gateway policy that you configured is working by using a device with the Cloudflare One Client installed to reach an internal application or external website.

If you cannot reach an application protected by Access or an external application through Gateway as expected, Cloudflare recommends starting with reviewing your Cloudflare One Client configuration.

1.1. Troubleshoot the Cloudflare One Client

If your manual test fails, troubleshoot the Cloudflare One Client. Cloudflare recommends starting with reviewing your Cloudflare One Client configuration because misconfiguration is the most common cause of connectivity issues.

1.2. Review analytics

Analytics provide visualizations of log data. To review Access or Gateway analytics:

  1. In the Cloudflare dashboard, go to Zero Trust > Insights > Analytics > Dashboards.
  2. Select Access event analytics for a summary of login events or Application Access Report for a summary of overall Access Activity.
  3. Select the HTTP request analytics, DNS query analytics or Network session analytics depending on your Gateway investigation scope.

1.3. Review logs

Logs provide event-level (such as an authentication attempt or a DNS query) visibility into your Cloudflare One environment.

To review traffic activity for applications protected by Access:

  1. In the Cloudflare dashboard, go to Zero Trust > Insights > Logs.
  2. Select Access authentication logs.
  3. Review the per-request logs for your application.

To review traffic activity in the Gateway logs:

  1. In the Cloudflare dashboard, go to Zero Trust > Insights > Logs.
  2. Select HTTP request logs, Network logs, or DNS query logs depending on your investigation scope.

Refer to Troubleshoot Gateway to troubleshoot common issues with Gateway egress policies.

2. Monitor your policies and device connectivity

After you confirm your policies work by testing manually, use DEX to monitor connectivity and performance over time.

Refer to Digital Experience Monitoring (DEX) for more information.

Example use case

  • Imagine that you have three devices, with the Cloudflare One Client installed, set up in your testing environment.
  • You have set up a Cloudflare Tunnel and an Access policy for your internal wiki that is available at wiki.acme.org.
  • You manually tested the three Cloudflare One Client devices, and you confirmed they can all reach wiki.acme.org.
  • You want to set up automated connectivity and performance testing to wiki.acme.org for each of these Cloudflare One Client devices so you can monitor them over time.
  • You set up a DEX test, and it sends an HTTP GET request to wiki.acme.org from all three devices on a five minute interval.
  • If device connectivity drops, or if there are performance problems, you can see the DEX test results to troubleshoot the problem.

2.1. Create a DEX test

Refer to DEX tests for more information.

HTTP test results

2.2. Set up notifications

Refer to DEX Notifications for more information on DEX-specific notifications.

Device anomaly notification setup

Customers who want to be notified when Cloudflare detects a spike or drop in the number of devices connected to the Cloudflare One Client can create a Device connectivity anomaly notification.

To create a device connectivity anomaly notification:

  1. In the Cloudflare dashboard, go to the Notifications page.

  2. Select Add.

  3. Find Product DEX and Alert type Device connectivity anomaly, and choose Select.

  4. Name the notification.

  5. Enter an email address to receive the notifications or set up a webhook.

  6. (Optional) Specify any additional options for the notification, if required. For example, some notifications require that you select one or more domains or services.

  7. Select Create.

Refer to Notifications for more information on editing, testing, and disabling notifications.

Conclusion

Once your policies are live, you can use DEX tests and notifications to ensure your team has secure, reliable access to internal and external resources.

:::tip[How it all works together]

To learn how to use Logs, Analytics, and DEX together during real-world situations, like onboarding, daily monitoring, and troubleshooting, refer to Insights for more example use cases.

:::

这篇文档对你有帮助吗？
想留言或继续讨论？请到 Cyberforums 赛博论坛参与。 参与讨论 / 回复