Screenshot API Usage Logs
Usage logs are invaluable for diagnosing issues, optimizing workflows, and monitoring performance when utilizing the Screenshot API. By reviewing these logs, you can swiftly identify and address any errors or discrepancies that may occur during usage.
Furthermore, usage logs offer crucial insights into account usage patterns. By tracking metrics like request volume and captured websites, users can refine their strategies and allocate resources more efficiently.
Additionally, usage logs facilitate tracking the destination of screenshots. This feature proves especially beneficial for monitoring changes and ensuring updates are implemented correctly, particularly when capturing screenshots of the user's own website.
In summary, access to usage logs enhances the effectiveness of the Screenshot API, offering insights that inform optimization efforts and streamline issue resolution processes.
Accessing Usage Logs on Add Screenshots
You can find usage logs for your website screenshots on the Usage Logs page within the Add Screenshots portal.
These logs typically include the following information, depending on the request type and status:
- Date - Date and time of the screenshot request
- Request URL - The requested website URL (e.g., example.com)
- Website URL - Final website URL after redirection (e.g., https://www.example.com/)
- Status Code - HTTP status code of the web response (e.g., 200 OK, 201 CREATED)
- IP Address - IP address of the requesting client
- Country Code - Country code of the requesting client
- Referrer - Referring website
- Region - Screenshot API region
- Job ID - Unique identifier for multi or bulk screenshot requests
- Error - Debug information returned by the website, if applicable
- Storage - Name of the storage provider (e.g., S3, Azure)
- Image - URL of the screenshot image
- Image Old - URL of the archived image for track changes
- Image Diff - URL of the diff image comparison for track changes
Below is an example of usage log entries:
