Cloudflare is a platform that is built to improve the security, performance, and reliability of systems connected to the Internet. It primarily does this by serving as a reverse proxy for your web traffic. Your traffic flows through Cloudflare where rules and optimizations are applied to meet its goals.
Cloudflare is in a position where it has great visibility into your traffic and web performance. Dynatrace can collect this information and make it available in Dynatrace for use monitoring and analytics purposes in context with the rest of your Dynatrace information. The extension queries various APIs to collect metrics as well as notification history for ingestion into Dynatrace.
Metrics
Review the list of feature sets to see which metrics are collected depending on the enabled feature sets.
Log events
Notification history
If enabled, a log event will be ingested for each notification event that shows up within your notification history.
Metrics and events are pulled from the Cloudflare API and so access to this API alongside a token with proper permissions is required.
To access 1-minute granularity data for HTTP-traffic a paid Cloudflare account is required as this information is not available over API for 'free' accounts.
Requirements
- Minimum Dynatrace environment and ActiveGate version 1.269
- A paid Cloudflare account
- Access to Cloudflare API and a token with required permissions
Dynatrace configuration
Find 'Cloudflare' in the in-product Extensions or Hub page and activate (if offline you can download the extension from this Hub page in the 'Release notes' section and install as you would a custom extension).
Monitoring configurations
Once activated in your environment you can create monitoring configurations. Each monitoring configuration can have one or more Cloudflare accounts
First select the desired ActiveGate group that will run the monitoring configuration.
Feature sets
Review the available feature sets to determine which you want to enable and collect. The enabled feature sets will effect which APIs are called.
Licensing
There is no charge for obtaining the extension, only for the data (metrics & events) that the extension ingests. The details of license consumption will depend on which licensing model you are using. This will either be Dynatrace classic licensing or the Dynatrace Platform Subscription (DPS) model.
Metrics
License consumption is based on the number of metric data points ingested. The following formula will provide approximate annual data points ingested by feature set. Note that many of these depend on the nature of the traffic being recieved by Cloudflare and so may change significanly over time.
Feature sets:
DNS Analytics
((1 * <dnsQueryLocation> * <dnsQueryResponseCode>)) * 525.6
HTTP Traffic
(6 + (1 * <sslProtocolVersion>) + (1 * <edgeResponseContentType) + (4 * <clientCountryName>) + (1 * <edgeResponseStatus>) + (1 * <threatPathingName)) * 525.6
Workers
((15 * <scriptName> * <status> * <usageModel> * <environmentName>) * 525.6
Log records
Log records will be ingested for notifications in the notification history of monitored Cloudflare accounts.
Log management and analytics (powered by Grail)
License consumption is based on the size (in bytes) of data ingested & processed, retained, and queried so there is not a single formula to estimate the total consumption from this extension. Consult the log management and analytics documentation for details on the other dimensions that will effect license consumption.
Classic licensing
In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of 100 DDUs per Gigabyte of log records ingested.
Log monitoring classic
In log monitoring classic, license consumption is based on the number of ingested log records.
Classic licensing
In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of .0005 DDUs per ingested log record.
Multiply estimated ingested log records by .0005 to estimate DDU usage from log records.
