Basics
- About the web interface controls
- Always-on DDoS mitigation
- Browser recommendations when using the Fastly web interface
- Content and its delivery
- Fastly POP locations
- Getting started with Fastly
- How caching and CDNs work
- How Fastly's CDN Service works
- HTTP status codes cached by default
- Self-provisioned Fastly services
- Sign up and create your first service
- Working with services
Domains & Origins
Performance
Basics
Dictionaries
Domains & Origins
- Changing origins based on user location
- Connecting to origins
- Enabling global POPs
- Failover configuration
- IPv6 support
- Maintaining separate HTTP and HTTPS requests to origin servers
- Routing assets to different origins
- Setting up redundant origin servers
- Specifying an override host
- Using Fastly with apex domains
Request settings
Cache settings
Headers
Responses
Performance
- About Dynamic Servers
- Cache control tutorial
- Caching configuration best practices
- Controlling caching
- Creating and using pools with Dynamic Servers
- Creating and using server entries with Dynamic Servers
- Enabling API caching
- Enabling automatic gzipping
- Failure modes with large files
- HTTP/2 server push
- Implementing API cache control
- Making query strings agnostic
- Request collapsing
- Segmented Caching
- Serving stale content
- Setting Surrogate-Key headers based on a URL
- Setting Surrogate-Key headers for Amazon S3 origins
- Streaming Miss
Purging
Custom VCL
- Accept-Language header VCL features
- Authenticating before returning a request
- Basic authentication
- Creating location-based tagging
- Custom responses that don't hit origin servers
- Delivering different content to different devices
- Enabling URL token validation
- Guide to VCL
- Isolating header values without regular expressions
- Manipulating the cache key
- IP geolocation variables: Migrating to the new dataset
- Overriding which IP address the geolocation features use
- Response Cookie handling
- Support for the Edge-Control header
- Understanding the different PASS action behaviors
- Using edge side includes (ESI)
- VCL regular expression cheat sheet
Image optimization
Video
Access Control Lists
Monitoring and testing
Securing communications
Security measures
TLS
- Domain validation for TLS certificates
- Enabling HSTS through Fastly
- Forcing a TLS redirect
- Managing domains on TLS certificates
- Serving HTTPS traffic using certificates you manage
- Serving HTTPS traffic using Fastly-managed certificates
- Setting up free TLS
- TLS key and certificate replacement
- TLS termination
Web Application Firewall
Logging endpoints
- Log streaming: Amazon S3
- Log streaming: Microsoft Azure Blob Storage
- Log streaming: Cloud Files
- Log streaming: Datadog
- Log streaming: DigitalOcean Spaces
- Log streaming: Elasticsearch
- Log streaming: FTP
- Log streaming: Google BigQuery
- Log streaming: Google Cloud Storage
- Log streaming: Honeycomb
- Log streaming: Kafka
- Log streaming: Log Shuttle
- Log streaming: LogDNA
- Log streaming: Logentries
- Log streaming: Loggly
- Log streaming: Heroku's Logplex
- Log streaming: OpenStack
- Log streaming: Papertrail
- Log streaming: Scalyr
- Log streaming: SFTP
- Log streaming: Splunk
- Log streaming: Sumo Logic
- Log streaming: Syslog
Non-Fastly services
Streaming logs
Debugging techniques
Common errors
Account management
Billing
User access and control
Monitoring account activity with event logs
Last updated September 21, 2018
Event logs keep track of events related to your services, account, and users. You can use event logs to determine which changes were made and by whom. For example, you can use them to:
- see who activated the most recent version of your service
- review who logged in to your account via the web interface
- learn which users have two-factor authentication enabled
- view recent service configuration setting changes
Use the Fastly API to retrieve a service's event logs or view a limited subset of those logs via the web interface.
Accessing event logs via the web interface
The web interface displays the last 20 service-related events for the selected service. Events related to users and accounts are not displayed in the web interface.
Follow these instructions to access the event logs for a service:
- Log in to the Fastly web interface and click the Configure link.
-
The most recent service-related events are displayed near the bottom of the page, in the Event log area.
NOTE: Event log data is currently retained indefinitely.
Accessing event logs via the API
The /events
API endpoint can be used to retrieve a service's event logs. You can filter these events by user_id
, service_id
, customer_id
, and event_type
. For example, you could make the following API call in a terminal application to view all recent events:
1
curl -g -H "Fastly-Key: FASTLY_API_TOKEN" https://api.fastly.com/events?filter[customer_id]=x4xCwxxJxGCx123Rx5xTx&page[number]=1&page[size]=1
The response will look like this:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
{
"data": [
{
"attributes": {
"admin": false,
"created_at": "2016-06-06T20:05:10Z",
"customer_id": "x4xCwxxJxGCx123Rx5xTx",
"description": "Version 2 was activated",
"event_type": "version.activate",
"ip": "127.0.0.0",
"metadata": {
"version_number": 2
},
"service_id": "SU1Z0isxPaozGVKXdv0eY",
"user_id": "4Pp0BW3UkBEJhG3N0kovLP"
},
"id": "5IH1QmNSV1Qi7jXc4oIZlZ",
"type": "event"
}
],
"links": {
"last": "https://api.fastly.com/events?filter[customer_id]=x4xCwxxJxGCx123Rx5xTx&page[number]=1&page[size]=1"
}
}
See the API documentation for more information.
Back to Top