Fastly Integration
Edge request metrics, cache efficiency, and Compute@Edge function monitoring for Fastly. Stream real-time logs and correlate edge performance with backend service health using AI anomaly detection.
How It Works
Configure Fastly Real-Time Logging
Enable Fastly real-time logging on your service configuration. Add TigerOps as an HTTPS logging endpoint and configure your VCL log format to include request, cache, and timing fields.
Enable Stats API Polling
Provide your Fastly API token to TigerOps for polling the Fastly Stats API. TigerOps fetches edge metrics (requests, hit ratio, bandwidth) per service and POP at 1-minute granularity.
Instrument Compute@Edge Functions
Add TigerOps OpenTelemetry SDK calls to your Compute@Edge Rust or JavaScript functions. Emit custom spans and metrics from edge functions alongside auto-instrumented request timing.
Build Edge Performance Dashboards
TigerOps auto-creates Fastly dashboards covering cache hit ratios, error rates by origin, TTFB percentiles per POP, and Compute@Edge function duration histograms.
What You Get Out of the Box
Real-Time Log Streaming
Stream Fastly access logs to TigerOps via the HTTPS logging endpoint with sub-second delivery. Parse VCL log format fields including cache state (HIT, MISS, PASS), backend timing, and restart counts.
Cache Hit Ratio and Efficiency
Track cache HIT, MISS, PASS, and SYNTH rates per service, hostname, and URL pattern. TigerOps alerts when hit ratios drop below baseline and identifies which URL patterns are causing cache misses.
Compute@Edge Function Monitoring
Monitor Compute@Edge function execution time, memory usage, WebAssembly instantiation latency, and error rates. AI detects performance regressions across function deployments.
POP-Level Performance Breakdown
Segment request metrics and cache ratios by Fastly POP (point of presence). Identify regional performance outliers and misconfigured backend origins causing elevated latency in specific POPs.
Origin Shield Monitoring
Track Fastly Origin Shield usage — requests served from the shielding POP vs. forwarded to origin. Monitor shielding effectiveness and detect degraded shielding performance that increases origin load.
Image Optimization and I/O Metrics
Monitor Fastly Image Optimizer transformation counts, output byte savings, and cache rates per image variant. TigerOps tracks I/O pipeline performance and alerts on transformation error spikes.
Fastly Logging Endpoint via Terraform
Configure the Fastly HTTPS logging endpoint for TigerOps using the Fastly Terraform provider.
resource "fastly_service_vcl" "myservice" {
name = "my-production-service"
# TigerOps HTTPS logging endpoint
logging_https {
name = "tigerops"
url = "https://ingest.atatus.net/fastly/logs"
request_max_entries = 500
request_max_bytes = 0
header_name = "Authorization"
header_value = "Bearer ${var.tigerops_api_key}"
content_type = "application/json"
method = "POST"
json_format = "2" # newline-delimited JSON
# Log format: cache status, timing, and request metadata
format = jsonencode({
timestamp = "%{begin:%Y-%m-%dT%H:%M:%S}t"
service_id = "%{req.service_id}V"
host = "%{req.http.Host}V"
url = "%{req.url}V"
method = "%{req.method}V"
status = "%{resp.status}V"
cache_state = "%{fastly_info.state}V"
is_h2 = "%{if(fastly.ff.visits_this_service == 0, resp.is_locally_generated, resp.proto == "HTTP/2")}V"
ttfb_ms = "%D"
bytes_sent = "%B"
pop = "%{server.datacenter}V"
})
}
}Common Questions
How does TigerOps receive Fastly real-time logs?
Configure a Fastly HTTPS logging endpoint pointing to https://ingest.atatus.net/fastly/logs with your TigerOps API key in the Authorization header. Use the Fastly log streaming UI, API, or Terraform provider to apply it to your service.
Can TigerOps monitor Fastly Compute@Edge functions written in Rust?
Yes. Add the TigerOps OpenTelemetry Rust SDK to your Compute@Edge project. The SDK emits spans and custom metrics from your WASM function via the Fastly backend fetch mechanism to the TigerOps OTLP endpoint.
Does TigerOps support Fastly's real-time analytics API?
Yes. TigerOps polls the Fastly Real-Time Analytics API (/v1/channel/{service_id}/ts/h) every 60 seconds and stores the aggregate request, hit, miss, error, and bandwidth metrics alongside your granular log data.
How do I track Fastly configuration deployments in TigerOps?
Use the Fastly Webhook integration to send service activation events to TigerOps. TigerOps marks deployment events on metric timelines, making it easy to correlate VCL changes with cache ratio or error rate shifts.
Can TigerOps alert me when Fastly cache hit ratio drops significantly?
Yes. TigerOps uses AI-learned baselines per service and per URL pattern. When cache hit ratio drops below your baseline by a configurable threshold, TigerOps fires an alert with the specific URL patterns responsible for the drop.
Complete Visibility from Fastly Edge to Backend
Real-time log streaming, cache hit rate monitoring, and Compute@Edge performance tracking. Connect in 5 minutes.