List view
# Features ## Control - [MI] Stopping proxy service / API / tasks / Inbound Endpoints - [MI] Change log level - [MI] Enable tracing - [MI] Enable stats - [MI] Enable wire logs - [MI] Enable open telemetry - [Bal] Change log level - [MI] view node stats - [Bal] view node stats Limitations - Only actions needed to damage control, not management. The effect of control does not persist. ## Monitor Active monitoring. Fixed historic information. No alerting or notifications, No automatic actions based on the monitoring. - At a glance status view - Per-component status is shown - Information for the view is gathered from multiple sources. Logs, tracing stats. - Number of integrations - Troubleshoot (Log retention not guaranteed) - Filter logs based on time, severity and source - Download information based on the filter # Architecture - Reuse parts of existing ICP Java code base - No external databases - Use disk as an index and a cache
Overdue by 1 year(s)•Due by November 14, 2024# Feature scope for M2 - Control - [MI] Enable wire logs, Stopping proxy service / tasks - Monitoring - At glance view pulls data from multiple data sources - Troubleshoot - Show multiple channels of data (carbon log, wirelogs, telemetry logs) UIs for control # Architectural scope for M2 - Improve data correlation strategy. Test with a large data volume. - Improve number of API calls batching - Improve log APIs with range support
Overdue by 1 year(s)•Due by October 31, 2024# Features - Control - Enable tracing, Enable wire logs - Monitoring - At a glance, show all deployed components and nodes. This milestone is based only on the product's API and, therefore is limited in status info. - Troubleshooting - showing wso2carbon.log content from multiple nodes. # Architecture - Reuse current ( MI/ ICP) APIs for components - Reuse the log API from MI - Create a new log API in ICP - Show error status for artifact where info available in MI such as CAPPs
Overdue by 1 year(s)•Due by October 14, 2024•1/8 issues closed