Elastic Collector Profile (Beta)

Detailed video of configuring the Elastic Collector Profile

Note

To enable this feature, please contact our HPE OpsRamp support team to activate the feature flag.

An Elastic Collector Profile is a scalable collector profile that lets you manage resource load by creating and removing collector profile replicas as needed.
It addresses the limitations of standard collector profiles, which can become overburdened and cannot efficiently handle large or fluctuating numbers of resources.
Elastic collector profiles enable:

Scale up operations: When the number of resources exceeds the capacity of a single collector profile, you can perform a scale-up operation. This creates a new replica profile, with resources evenly distributed between the master and the replica profiles.
Scale down operations: When resource demand decreases and some replica profiles are no longer needed, you can perform a scale-down operation. This deletes the last replica profile and redistributes its resources across the remaining active profiles.
Rebalancing resources: Resources attached to gateway collector profiles are redistributed across all active profiles (master and replicas) to ensure:
- No single profile is overloaded.
- Optimal utilization of system resources.

Elastic collector profiles provide controlled scalability and improved load distribution while keeping scaling decisions in your hands.

Feature Insight

	Scaleup	Scaledown	Rebalance
Purpose	Expand collector capacity by adding replicas	Reduce the number of replicas when resource utilization is low	Manually redistribute resources if automatic redistribution fails after Scaleup
Key Features	Automatic Deployment of replicas when triggereds Auto-Registration & Redistribution of resources Sequential Scaling	Deletion of the last deployed replica Resource Redistribution Cluster Optimization by releasing CPU and memory	Redistribute resources evenly across all replicas Ensures all replicas, including Master, have balanced resources
Use cases	Handling large-scale resources when a single replica is overloaded	When system resource utilization (CPU, memory) is consistently low and and minimal workload per replica	When automatic load balancing fails, requiring manual intervention to ensure efficient distribution
Key Action	Deploys new replicas and redistributes resources	Removes the last replica and redistributes resources	Ensures even resource distribution across replicas

What is importance of Elastic Collector Profiles?

The standard collector profiles are following limitations which are well address using Elastic.

Overburdened Profiles: A single management profile cannot efficiently handle all resources, leading to performance bottlenecks.
Lack of Scalability: Default profiles cannot scale dynamically to accommodate fluctuating resource requirements.

Elastic collector profiles overcome above limitations by introducing scaling and load balancing using below features:

Scale-Up and Scale-Down Operations:
- When the number of resources exceeds the capacity of a single collector profile:
  - Scale-Up: A new replica profile is dynamically created to handle the additional resources, with resources evenly distributed across the original profile and the newly created replica profile.
- During periods of low demand:
  - Scale-Down: Unused replica profiles are deleted, and their resources are redistributed.
Dynamic Resource Rebalancing:
- Resources attached to the gateway collector profiles are redistributed across all active profiles (master and replica).
- Rebalancing ensures:
  - No single profile is overburdened.
  - Optimal utilization of system resources.

Elastic Collector Profile Limitations

Existing collector profiles profiles with standard type cannot be upgraded as elastic.
Only the NextGen Gateway will support elastic profiles.