Minimal Documentation Lynfera

• The version of the build tools
• Warnings or errors encountered during the build process
• Details about the files and dependencies that were installed, compiled, or built during the deployment

Build Logs working

Build logs are generated at build time for all Deployments. The logs are similar to your framework's Build Command output, with a few minor additions from the Lynfera build system. Once a build is complete, no new logs will be recorded.

In addition to the list of build actions, you can also find errors or warnings. These are highlighted with different colors, such as yellow for warnings and red for errors. This color coding makes it flexible to investigate why your build failed and which part of your website is affected.

Each type are:

• INFO - General logs
• WARN - Warnings
• ERROR - Errors. Mostly this shows why your build fails
• DECOR - Decorations. These are just branding decorations. It also shows build specifications

Saving logs

You can download the logs as a txt file.

Log Retention

Logs are stored for up to 25 days. Logs older than this period are automatically deleted and cannot be recovered.

Log entries include standard log levels such as info, warn, and error. For performance and decoration-related logs (DECOR), only the most recent 5 days of data are retained.

Retention limits help balance observability, storage efficiency, and system performance while keeping recent logs readily available for troubleshooting.

Overview

Web Analytics provides comprehensive insights into your website's visitors, allowing you to track the top visited pages, referrers for a specific page, and demographics like location, operating systems, and browser information. Lynfera's Web Analytics offers:

• Privacy: Web Analytics only stores anonymized data and does not use cookies, providing data for you while respecting your visitors' privacy and web experience.
• Integrated Infrastructure: Web Analytics is built into the Lynfera platform and accessible from your project's dashboard so there's no need for third-party services for detailed visitor insights.

Visitors

Visitors are identified from incoming HTTP requests to your project. Analytics are primarily calculated from non-cached requests, which means only requests that reach our servers are tracked. As a result, visitor metrics may represent a subset of total traffic.

We collect lightweight request and client metadata—such as paths, response status, device type, and timestamps—to generate visitor counts, performance insights, and usage trends. No raw request bodies or application-level data are stored.

Analytics Views

Analytics are divided into focused views, each highlighting a specific aspect of your traffic and usage patterns.

• Overview shows total requests, unique requests, and average response time.
• Bandwidth displays request and response bandwidth usage.
• Top Pages highlights the mostrequested paths.
• OS Stats breaks down traffic by operating system and device type.

All views support selectable time ranges: last hour, 24 hours, 1 week, and 1 month. Overview and Bandwidth also support adjustable time intervals; interval customization requires a Pro account.

Chart Data

By default, the Unique visitors chart counts different IP addresses engaging with your site within a single day. If someone loads pages of your site on multiple different days, they will be counted as a unique visitor for each day. If you select the 24 hours filter, then the chart will plot different IP addresses engaging with your site within a single hour. If someone loads pages of your site during multiple different hours, they will be counted as a unique visitor for each hour. The Total unique visitors for your site will typically be less than the sum of daily or hourly values because the total counts IP addresses that are unique across the whole charted time period.

Bandwidth used tracks all visitor traffic including 304 responses and 404 errors. This does not include Lynfera activity such as building and deploying your site. Bandwidth is primarily calculated from response headers and represents the Content-Length of returned files.

Requests represent the total number of HTTP requests received by the server and may not reflect the actual number of users. This count is an approximation and can include requests for assets such as .js, .css, images, and other dependent files.

Analytics Retention

Analytics data is stored for up to 1 month. Data older than this period is automatically deleted and cannot be recovered.

Stored analytics include aggregated request metrics, performance data, and usage breakdowns such as pages, platforms, and bandwidth. Raw request payloads and application-level data are not retained.

Retention limits help ensure predictable storage usage and protect user privacy while still providing meaningful insights into recent traffic patterns.