Cloudflare Digital Experience Monitoring
Digital Experience Monitoring.
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноТолько чтение
Что умеет
- Accounts List: List all accounts in your Cloudflare account
- Set Active Account: Set active account to be used for tool calls that require accountId
- Dex Test Statistics: Analyze Cloudflare DEX Test Results by quartile given a Test ID
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
Digital Experience Monitoring. Get insight on critical application performance for your organization.
Список инструментов сервера (20)
Технические названия из tools/list. Нужны только разработчикам.
| accounts_list | List all accounts in your Cloudflare account |
| set_active_account | Set active account to be used for tool calls that require accountId |
| dex_test_statistics | Analyze Cloudflare DEX Test Results by quartile given a Test ID |
| dex_list_tests | Retrieve a list of all Cloudflare DEX Tests configured. |
| dex_http_test_details | Retrieve detailed time series results for an HTTP DEX test by id. |
| dex_traceroute_test_details | Retrieve detailed time series results for a Traceroute DEX test by id. |
| dex_traceroute_test_network_path | Retrieve aggregate network path data for a Traceroute DEX test by id. Use the dex_traceroute_test_result_network_path tool to further explore individual test runs hop-by-hop. |
| dex_traceroute_test_result_network_path | Retrieve the hop-by-hop network path for a specific Traceroute DEX test result by id. |
| dex_list_remote_capture_eligible_devices | Retrieve a list of devices eligible for remote captures. You'll need the device_id and user_email from this response in order to create a remote capture for a specific device. It can also be used as a generic source to find devices registered to the account, filtering by user email if necessary. |
| dex_create_remote_pcap | Create a remote packet capture (PCAP) for a device. This is a resource intensive and privacy-sensitive operation on a real user device.Always ask for confirmation from the user that the targeted email and device are correct before executing a capture |
| dex_create_remote_warp_diag | Create a remote Warp Diagnostic (WARP-diag) for a device. This is a resource intensive and privacy-sensitive operation on a real user device.Always ask for confirmation from the user that the targeted email and device are correct before executing a capture |
| dex_list_remote_captures | Retrieve a list of remote captures for device debugging, like PCAPs or WARP Diags. |
| dex_fleet_status_live | Retrieve details about the real-time status of the fleet of devices broken down by dimension (mode, status, colo, platform, version) |
| dex_fleet_status_over_time | Retrieve aggregate time series details about the status of the fleet of devices, or performance metrics for a specific device, over the specified time period. |
| dex_fleet_status_logs | Retrieve raw fleet status device logs with a variety of levels of granularity and filtering. Use `source=last_seen` to view logs showing the last known state per device within the specified time period. Use `source=hourly` to view logs showing an hourly rollup per device where values are the average value of allevents within the time period. Use `source=raw` to view all logs for the specified period. |
| dex_list_warp_change_events | View logs of events when users toggle WARP on or off, or change configurations. |
| dex_list_colos | View a list of Cloudflare colos sorted alphabetically or by frequency encountered in fleet status or DEX test data. |
| dex_list_remote_warp_diag_contents | Given a WARP diag remote capture id and device_id, returns a list of the files contained in the archive. |
| dex_explore_remote_warp_diag_output | Explore the contents of remote capture WARP diag archive filepaths returned by the dex_list_remote_warp_diag_contents tool for analysis. |
| dex_analyze_warp_diag | Analyze successful WARP-diag remote captures for common issues. This should be the first place you start when trying to narrow down device-level issues with WARP. |