In this section you'll find information about debugging, logging, error codes, and how to resolve common errors. EdgeWorkers provides four different debugging and logging options.
|Standard debug headers||Provides general status and EdgeWorker information (id, version, and name) for the executed EdgeWorkers function.|
|Enhanced debug headers||As a best practice you should enable enhanced debug headers.|
These enhanced debug trace headers provide actionable details that will help you troubleshoot your EdgeWorkers.
You can also use variable substitution to include dynamic data in the EdgeWorkers logs.
|Log Delivery for EdgeWorkers||Provides status and failure information for your EdgeWorker IDs over a specified period of time in an LDS server log.|
Review these resources and tips that can also help you troubleshoot and test your EdgeWorkers:
- To handle exceptions cleanly write
- Refer to the Limitations section for information about what you should keep in mind when designing your EdgeWorkers functions. You can also review a list of the currently supported delivery products.
- Use Site Failover to define what action to take in the event that an EdgeWorkers function fails.
- Note that EdgeWorkers functions are supported on both the Enhanced TLS and Standard TLS networks. At the moment you need to contact your Akamai representative or reach out via the Serverless Slack channel to use Standard TLS.
Updated about 1 month ago