Service management and use cases
Service management was another crucial organization function that was not formalized so far. Now, Cassandra was deployed in a cluster; application and web servers had their own clusters. The backlog of features to have service supportability and application supportability as well as service management needs were huge, but the top priority was to have a central log containing the following contents:
- Application logs
- Network logs
- Performance metrics
- Audit data
- Monitoring data
All of these were to be classified into different classes such as <APPLICATION>:INFO, <APPLICATION>:WARNING, <APPLICATION>:ERROR, <NETWORK>:INFO, <NETWORK>:WARNING, <NETWORK>:ERROR, <METRIC>:LOW, <METRIC>:25TH, <METRIC>:50TH, <METRIC>:75TH, <METRIC>:90TH ...
Get Cassandra Design Patterns - Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
