Skpr v1.1 is here, and it's a significant step forward for developer self-service and platform security.
This release expands what you can see, gives you more control over how you see it, and hardens the platform against the kind of traffic that doesn't belong there.
Here's what's new:
Date range control for metrics
You can now set the metrics window directly in the Skpr WebUI.
Previously, dashboards showed a fixed view of your data. Now you can select a custom date range, with support for up to 60 days of historical metrics.
This gives development teams the flexibility to investigate specific incidents, compare performance across time periods, or review long-running trends without leaving the UI.
CDN upload and download metrics
We've added upload and download metrics for your CDN directly to the dashboard.
These sit alongside the response time and HTTP response code data we covered in our The Power of P95/P99 post, giving you a more complete picture of traffic flowing through the edge.
Application metrics
Skpr now supports custom application metrics, surfaced directly in the WebUI.
This feature is framework-agnostic, but for teams running Drupal the practical value is significant. Your developers can expose and monitor their own application-level metrics without needing to go outside the platform to diagnose issues.
For example, teams are already using this to track:
- Total node count
- Total revision count
- Active session count
- Queue size
This kind of deep visibility makes it easier to spot trends, diagnose issues, and understand how an application is actually behaving in production.
JA4 fingerprinting support
Skpr now supports JA4 fingerprinting.
JA4 is a network fingerprinting standard that identifies clients based on their TLS handshake characteristics, independent of their declared user agent. This matters because sophisticated bots and bad actors frequently spoof or rotate user agents to avoid detection. JA4 fingerprinting gives the platform a more reliable signal for identifying that traffic.
In practical terms: if you're dealing with a DDoS event or bot traffic that's evading your existing rules, the platform now has better tools to identify and action it. Skpr handles the blocking at the WAF level, this isn't a configuration task for your development team.
Hardened security context for application runtimes
We've applied further hardening to the security context for application runtimes. This is an infrastructure-level improvement that reduces the attack surface for applications running on the platform.
We won't go into detail here, but it's part of our ongoing commitment to defence-in-depth across the Skpr stack.
Questions or feedback? Get in touch with the Skpr team.