Cluster Telemetry Metric Registration With RBAC Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing telemetry architectures in distributed cluster networks are inflexible and lack dynamic mechanisms for adding new metric data sets, data producers, or consumers, and do not provide role-based access control (RBAC) for telemetry data access.
Innovation Solution
Implement a subscription-based telemetry system with dynamic registration of new metrics and RBAC-based access control, allowing users to dynamically subscribe to telemetry data through preferred transports and ensuring access is restricted based on user roles.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a fixed telemetry architecture is used, then system simplicity is maintained, but flexibility to add new metrics and dynamic registration is lost
Solution Approach 1:
The patent implements dynamic registration of telemetry metrics through runtime APIs that allow new metrics to be added without system restart. The telemetry system transitions from a static configuration to a dynamic one where metrics, data producers, and consumers can be registered and unregistered during operation, directly resolving the contradiction between adaptability and complexity.
Solution Approach 2:
The patent segments the telemetry system into independent modular components: metrics registry, data producers, data consumers, and transport mechanisms. Each component can be independently registered, configured, and managed through APIs, allowing flexible addition of new metrics without affecting the entire system structure.
2Adaptability or versatility
If dynamic registration of new metrics is implemented, then system flexibility is improved, but access control security mechanisms are compromised
Solution Approach 1:
The patent implements Role-Based Access Control (RBAC) that is configured in advance before dynamic metric registration occurs. RBAC policies define which roles can access which metrics, and this access control framework is established beforehand to govern subsequent dynamic registrations, ensuring security is built into the flexible architecture from the start.
Solution Approach 2:
The patent introduces an RBAC intermediary layer between the dynamic metric registration system and the actual data access. This intermediary validates access requests against predefined role policies, mediating between the flexibility of dynamic registration and the security requirements of access control.
3Adaptability or versatility
If RBAC rules are dynamically allocated, then adaptability to new metrics is achieved, but system complexity increases
Solution Approach 1:
The patent implements a universal RBAC framework that works across all metric types and data producers/consumers. The same RBAC mechanisms and role definitions apply universally to any dynamically registered metric, eliminating the need for separate access control systems for different metric types and reducing overall management complexity.
Data Source
AI summary
A telemetry processing system in a cluster network generates telemetry data from a plurality of telemetry producers and formats it into a structured format for storage. Producers define new metrics for use in a running network. Role-based access control (RBAC) levels for metrics are mapped to users based on roles within an organization using the produced telemetry data. A final RBAC level of a new metric is established through a recommendation and validation process between the producer and an RBAC recommendation module. Once validated, the final RBAC level and new metric are stored in a telemetry catalog. Telemetry datasets for the new metric are sent for storage and transmitted to appropriate users based on RBAC rules including the final RBAC level.