Product: Difference between revisions
No edit summary |
No edit summary |
||
Line 18: | Line 18: | ||
TO Process: | TO Process: | ||
* http://www.programmableweb.com/news/tools-to-monitor-and-visualize-microservices-architecture/analysis/2016/12/14 | * http://www.programmableweb.com/news/tools-to-monitor-and-visualize-microservices-architecture/analysis/2016/12/14 | ||
=Use Cases= | |||
* '''Load Testing''' automates advancement to criteria. | |||
* '''Complex Failure Diagnostics''' correlation, causality vs. correlation. |
Latest revision as of 14:33, 30 August 2017
Placeholder is a set of methodologies and tools that assist a large system operator, by automatically identifying the rood causes of abnormal behavior, such as obvious crashes or more subtle episodic or incremental performance degradation.
Even when an unequivocal root cause cannot be inferred, Placeholder will speed up the root cause analysis by providing a significantly reduced area for human investigation.
The value the product brings while performing steady state monitoring (passive mode) is that it applies a set of infrastructure specific rules, curated from a large number of past situations, to predict
The product can also be used in active mode, where it cooperates with a load generator to stress the system and actively find its weak points.
Related:
- Business Scenario-Based Performance Monitoring and Diagnosis
- https://access.redhat.com/products/red-hat-insights
- http://www.hawkular.org/overview/
TO Process:
Use Cases
- Load Testing automates advancement to criteria.
- Complex Failure Diagnostics correlation, causality vs. correlation.