Monitoring Quick Reference

Monitoring Quick Reference#

Quick reference guide for common monitoring tasks, metrics explanation, and troubleshooting.


Quick Navigation#

Accessing Features#

FeaturePathKeyboard
HTTP TrafficMonitoring โ†’ HTTP Traffic tabTab 1
DNS MetricsMonitoring โ†’ DNS Metrics tabTab 2
DNS AnalyticsMonitoring โ†’ DNS Analytics tabTab 3
UptimeMonitoring โ†’ Uptime tabTab 4

Recommended First Steps#

  1. New Users: Start with Monitoring Overview
  2. Traffic Issues: Go to HTTP Traffic
  3. Slow DNS: Check DNS Metrics
  4. Application Down: See Uptime Monitoring
  5. Detailed Analysis: Review DNS Analytics

Metrics at a Glance#

HTTP Traffic Metrics#

MetricHealthyWarningCritical
Cache Hit Rate80%+50-80%<50%
Response Time<100ms100-500ms>500ms
ThreatsLow/stableIncreasingSpiking
BandwidthStableGrowingExcessive

DNS Metrics#

MetricHealthyWarningCritical
Query Time<100ms100-500ms>500ms
DNSSEC Valid100%95-100%<95%
Query VolumeStableยฑ25% change>50% change
Record DistributionExpectedMinor changesUnexpected types

Uptime Metrics#

MetricHealthyWarningCritical
Response Time<200ms200-500ms>500ms
Uptime99%+95-99%<95%
Certificate Days>30 days15-30 days<15 days
Availability100%99%+<99%

Common Tasks#

Monitor Application Health#

Steps:

  1. Go to Uptime tab
  2. Select your application
  3. Check green status bar
  4. Review response time chart
  5. Verify uptime percentage > 99%

Time: 2-3 minutes

Analyze Traffic Patterns#

Steps:

  1. Open HTTP Traffic tab
  2. Set date range (last 7 days recommended)
  3. Review Traffic Over Time chart
  4. Check Cache Distribution pie chart
  5. Export data if needed

Time: 5-10 minutes

Check DNS Performance#

Steps:

  1. Click DNS Metrics tab
  2. Select application
  3. Review response time (target: <100ms)
  4. Check geographic distribution
  5. Verify no red indicators

Time: 2-3 minutes

Investigate Issue#

Steps:

  1. Identify issue type
  2. Go to relevant tab
  3. Check corresponding metric
  4. Review time period of issue
  5. Check related sections (logs, alerts)

Time: 10-15 minutes

Export Data for Report#

Steps:

  1. Open HTTP Traffic tab
  2. Set date range
  3. Click Export button
  4. CSV downloads automatically
  5. Open in spreadsheet application

Time: 1-2 minutes

Set Up Alerts#

Steps:

  1. Go to Alerts
  2. Create alert rule
  3. Choose condition (uptime, response time, etc.)
  4. Set threshold
  5. Configure notification

Time: 5 minutes


Problem Diagnosis#

Application Shows Downtime#

Check:

  1. Uptime tab - Current status?
  2. Status bar - When did it go red?
  3. Response time chart - Sudden drop?
  4. Application logs - Any errors?
  5. Infrastructure - Server status?

Most Common Causes:

  • Server crash/restart
  • Deployment issue
  • Resource exhaustion
  • Network problem
  • Database connection lost

Response Times Slow#

Check:

  1. Uptime tab - Response time trend?
  2. HTTP Traffic - Traffic spike?
  3. DNS Metrics - DNS delay?
  4. Application logs - Slow queries?
  5. System resources - CPU/Memory high?

Most Common Causes:

  • Increased traffic
  • Database slowdown
  • Memory leak
  • Inefficient code
  • Network latency

High Security Threats#

Check:

  1. HTTP Traffic - Threat count increasing?
  2. Top Countries - Attack source?
  3. Traffic Over Time - Pattern visible?
  4. Threat type - DDoS or other?
  5. Cloudflare logs - Attack details?

Most Common Causes:

  • DDoS attack
  • Scanning activity
  • Bot traffic
  • Exploit attempts
  • User data scraping

DNS Not Resolving#

Check:

  1. DNS Metrics - Response time?
  2. Query volume - Spike?
  3. Record types - Unexpected?
  4. DNSSEC - Valid?
  5. Geographic performance - Regional?

Most Common Causes:

  • DNS server down
  • Misconfigured records
  • TTL expired
  • Network issue
  • DNSSEC validation fail

Performance Optimization Tips#

Improve Response Time#

  • Scale horizontally
  • Optimize code/queries
  • Increase resources
  • Implement caching
  • Use CDN

Improve Cache Hit Rate#

  • Increase TTL
  • Remove cache exceptions
  • Cache more content
  • Optimize cache rules
  • Use cache busting

Reduce Traffic Volume#

  • Implement compression
  • Optimize images
  • Minify code
  • Reduce requests
  • Use async loading

Improve DNS Performance#

  • Use faster DNS provider
  • Implement DNS caching
  • Reduce record count
  • Optimize TTL
  • Use anycast DNS

Alert Configuration Guide#

Alert Types#

Performance Alerts:

  • Response time > 500ms
  • Cache hit rate < 80%
  • Uptime < 99%

Availability Alerts:

  • Application downtime
  • Service unavailable
  • Connection timeout

Security Alerts:

  • Threat spike > 1000/hour
  • DDoS detected
  • Unusual query patterns

Certificate Alerts:

  • Expiration < 30 days
  • Expired certificate
  • Invalid certificate

Setting Alert Thresholds#

Conservative (Proactive):

  • Response time > 300ms
  • Uptime < 99.5%
  • Threats > 500/hour

Balanced (Recommended):

  • Response time > 500ms
  • Uptime < 99%
  • Threats > 1000/hour

Aggressive (Critical Only):

  • Response time > 1000ms
  • Uptime < 95%
  • Application down only

Metrics Glossary#

HTTP Traffic Terms#

Cache Hit Rate: Percentage of requests served from cache (higher is better)

Bandwidth: Total data transferred (measured in GB/TB)

Unique Visitors: Count of distinct users (based on IP/browser)

Security Threats: Requests blocked by security rules

TTL: Time To Live - how long content stays cached

DNS Terms#

Query Time: Time for DNS server to respond (milliseconds)

Recursive Query: Resolver finds full answer for client

Non-Recursive Query: Resolver returns cached answer

DNSSEC: DNS Security Extensions - cryptographic verification

Zone: Domain and its DNS records

Uptime Terms#

Uptime: Percentage of time application is available

Response Time: Time between request and response

SLA: Service Level Agreement - uptime guarantee

RTO: Recovery Time Objective - max time to restore

RPO: Recovery Point Objective - max data loss acceptable


Keyboard Shortcuts#

ShortcutAction
Tab 1HTTP Traffic
Tab 2DNS Metrics
Tab 3DNS Analytics
Tab 4Uptime
RRefresh data
EExport data
/Search documentation

Useful Links#

Documentation:

Related:

External:


FAQ#

Q: How often is data updated? A: Uptime every 1-5 minutes, HTTP traffic daily, DNS metrics every 5-15 minutes.

Q: How long is data retained? A: Uptime indefinitely, HTTP traffic 30 days, DNS metrics 7 days.

Q: Can I set custom alert thresholds? A: Yes, see Alerts documentation.

Q: How do I export data? A: Click Export button in HTTP Traffic tab.

Q: What causes false outages? A: Monitoring endpoint down, firewall blocking, regional network issues.

Q: Can I monitor multiple applications? A: Yes, select different apps from dropdown in each tab.

Q: How do I improve response times? A: Scale application, optimize code, increase resources, use caching.

Q: What is normal uptime? A: 99%+ is excellent, 95-99% is acceptable, <95% needs investigation.