Platform.sh projects are accompanied by live infrastructure metrics that provide an overview of resource usage for environments.
Within the Console, metrics can be found for an environment under Metrics.
The information under Metrics shows usage metrics for:
Dedicated Gen 2 environments: each of the three hosts in your N+1 configuration and their average for the Production environment. Metrics aren’t available for other Dedicated Gen 2 environments (such as a staging environment), but are available for Grid environments (such as your development environments).
Dedicated Gen 3 environments: each of the three hosts and their average. These metrics are available for all of your Dedicated Gen 3 environments.
Grid environments: your service, app, and worker containers. These metrics are available for all of your Grid environments.
Infrastructure metrics are available on all regions except the legacy regions:
These regions will be upgraded in the future. If you’re on one of these regions and want infrastructure metrics now, migrate your project to a newer region.
All of the graphs show labels for the following thresholds:
Usage that crosses 80% results in a warning label.
Usage that crosses 90% results in a critical label.
On Dedicated Gen 3 and Grid environments, usage that crosses 100% results in a burst label.
The burst capability is available for containerized environments and allows a container to get more resources than it’s allocated. Burst is considered useful for infrequent activities that cause usage spikes, but these additional resources aren’t guaranteed.
The default thresholds aim to give you an idea of when your hosts/containers are close to running out of resources. The impact differs based on your specific apps and service. The values of the thresholds is purely informational.
For Dedicated Gen 2 environments, the thresholds are set for each host. If the resources are high and hovering close to the 100% threshold, you might want to consider:
For Dedicated Gen 3 environments, the thresholds are set for each container.
If you have one container in a temporary burst state but your host still has plenty of available resources, it might not be an issue as long as the site is functioning properly. Burst allows your container to use additional resources when they aren’t needed elsewhere.
If you have a container in a prolonged burst state, you might want to consider:
You can reallocate your existing resources if other containers have resources they aren’t using.
If you have multiple containers in a burst state, review your configuration or plan size.
For Grid environments, the thresholds are set for each container. If the resources are high and hovering close to the 100% threshold, you might want to consider:
If your containers are in a prolonged burst state, review your configuration or plan size because burst isn’t guaranteed for long periods. If the burst threshold is triggered for short, infrequent activities, it might not be an issue as long as the site is functioning properly. Burst allows your container to use additional resources when they aren’t required on the container’s host.
Measurements are taken for each metric every 1 minute. You can select a time frame over which to see these measurements for the entire Metrics view. In the primary three views, averages are shown over larger intervals.
|View||Time between measurements||Example|
|The last 15 minutes (15m)||1 minute||10:00, 10:01, 10:02|
|The last hour (1hr)||1 minute||10:00, 10:01, 10:02|
|The last 24 hours (24hr) for Dedicated and 8 hours (8hr) for Grid||20 minutes for Dedicated, 10 minutes for Grid||10:00, 10:20, 10:40, 11:00|
To zoom in on smaller intervals, select specific ranges in a graph.
The interval between measurements then changes based on the range you choose.
|View||Time between measurements|
|< 2 hours||1 minute|
|2 to 5 hours||5 minutes|
|5 to 8/24 hours||20 minutes|
Sometimes deployment activities (pushes, merges, syncs) can influence the underlying infrastructure. You don’t want to confuse a spike caused by a successful deploy with an issue that needs your attention.
To see how deployment activity influences the infrastructure, turn on Deployments on your metrics.
Each deployment activity appears as a line on each graph corresponding to the time the activity finished. To see information about the deployment activity, hover over the line. To see the build log for a specific deployment activity, click the line.