Grouping
Leverage advanced PerfectScale grouping to streamline your optimization process even for highly dynamic environments
Last updated
Leverage advanced PerfectScale grouping to streamline your optimization process even for highly dynamic environments
Last updated
The PerfectScale grouping configuration stands as a powerful tool, facilitating the aggregation of data pertaining to redundant workloads exhibiting similar patterns. By preventing overload through batches of identical information, it enables you to focus on what matters, thereby streamlining analysis processes.
Custom grouping is an aggregation rule that aggregates multiple workloads into a single entity (for example, all GitLab runners are aggregated into a single entity—the GitLab workload), merging their data (resource usage, limits, requests, etc.).
This feature is especially convenient when using Spark, GitLab, or any other operators that produce short-living small workloads that often reflect just a single pod in the cluster.
Go to the Settings tab on the left panel -> select Grouping -> click the +Add Profile button -> name the profile and put the needed values in the relevant fields -> click Save button.
Go to the Overview tab on the left panel -> find the cluster to which you want to apply the Grouping Profile and click gear button -> go to Customizations -> click on Add New Profile in the Custom Grouping Profile drop-down list -> name and configure your profile -> click the Save And Apply button -> click the Save Changes button.
Here is the list of configurable grouping fields:
name - the group name of the aggregated workloads
filter - a set of conditions that define to which workloads the grouping will be applied. The workloads that meet the conditions will be assigned to a group:
priority - (optional) indicates the filter's priority. This is particularly helpful when multiple filters match the workload.
owner_type - (case sensitive) the equivalent of Type in Podfit.
namespace - (case sensitive) checks if the workload belongs to the particular namespace
pod_regex - a regular expression identifies the workload by its name (for example: loki-.* searches for the workloads with names start with loki- and then have at least one more symbol).
containers_exists - checks if workload holds the list of the containers described in this filter.
target_workload - a meta workload represents the group of workloads matched by the filter.
workload_name - (mandatory) the name of the grouped workload to which workloads will be grouped.
workload_type - (mandatory) the type of the grouped workload to which workloads will be grouped.
workload_namespace - (optional) the namespace of the grouped workload to which workloads will be grouped.
container_grouping - an array of profiles for container grouping for the workload Custom Grouping entry. This is particularly helpful when the container names are auto-generated.
container_filter - a set of conditions that define to which containers the grouping will be applied (supports only regexes).
container_regex - a regular expression identifies the container by its name.
target_container - the container in which containers will be grouped by the entry.
You can seamlessly group short-lived workloads into a single entity using a grouping profile, which helps eliminate unnecessary clutter. This feature is particularly helpful when managing many short-lived workloads, allowing you to focus on the most important aspects. By grouping them, you can highlight the most relevant data, helping you prioritize actions and optimize your cluster more effectively.
To group short-living workloads, use the following configuration:
The Custom Grouping Preview feature allows you to quickly evaluate how the cluster will look after re-aggregation with the applied profile.
Click the Custom Grouping Preview button to navigate directly to the preview screen.
Select the cluster that you want to group with the Grouping Profile. Get an estimated number of workloads, namespaces, and clusters after the grouping is applied.
Choose to which data, whether aggregated or raw, you want to apply the Grouping profile along with the desired timeframe.
Filter workloads by column values in the workloads table and view the number of workloads in each group.
PerfectScale can auto-generate the Grouping profile with a single click.
We recommend you check and validate the auto-generated profiles before applying them to a cluster.
To auto-generate a Grouping Profile, go to the Overview tab on the left panel -> find the cluster to which you want to apply the Grouping Profile and click three dots button -> select Cluster Settings -> go to Customizations -> click Auto-Generate Profile-> name the profile and click Save button.
To apply Grouping Profile to the cluster, go to the Overview tab on the left panel -> find the cluster to which you want to apply the Grouping Profile and click gear button -> go to Customizations -> select the needed profile in the Custom Grouping Profile drop-down list.
To apply the profile to multiple clusters from a single view, use the Manage Assignments feature.
Go to the Settings tab on the left panel -> select the Grouping -> click the Manage Assignments button -> apply the profiles for the needed clusters -> click the Save Changes button.
There are two options for creating a Profile: tab or directly .
label_exists - checks if the specific key is attached to the workloads (single key or comma-separated list of keys).
NOTE: label keys should be provided in the Prometheus format.
Example: Kubernetes: app.kubernetes.io/instance
Prometheus: label_app_kubernetes_io_instance
namespace_regex - a regular expression identifies the namespace by its name.
NOTE: namespace_regex should be paired with some other filter condition.
Use Set as default checkbox to automatically assign the profile to the clusters.
NOTE: The manually assigned profile takes priority over the default one.
