Cluster Health & Overload Monitoring Platform (CHOMP) Feature Project
- jw4099
- Paul Carver
- pdelong6
Project Technical Lead:
Project Committer Details:
Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.
A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.
Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project. Candidates must self nominate by marking "Y" in the Self Nominate column below by Jan. 16th. Voting will take place January 17th.
Only Committers for a project are eligible to vote for a project’s Project Technical Lead.
Please see Akraino Technical Community Document section 3.1.3 for more detailed information.
Committer | Committer Company | Committer Contact Info | Committer Bio | Committer Picture | Self Nominate for PTL (Y/N) |
Use Case Details:
Feature | Description | Companies Participating / Committers | Requested Release / Timeline | Informational |
Operational Tools Augmentation | CHOMP (Cluster Health and Overload Monitoring Platform) will do log correlation for Akraino lifecycle management 1. Log-based metrics in CHOMP provide key visibility for operations teams beyond the existing traditional monitoring tools such as Prometheus 2. These KPIs could become the beginning of troubleshooting and root cause identification as NC becomes ready for production deployments 3. Broad categories include: a. Latencies for common Kubernetes procedures b. Failure details - insufficient memory or computing capacity c. Procedure details - restart backoffs, pod evictions prior to restarts d. Kubernetes Component Availability – loss of kube-proxy, scheduler, etc.h 4. Modular design and Configurable for easy addition of new log-based metrics as NC platform matures | AT&T | R1 | Impacted Blueprint Family - Network Cloud See next slide for additional details |