Coralogix TCO not only reduces your logging costs by up to two-thirds but also improves your ability to query, monitor, and manage your data, by allowing you to define the data pipeline your logs will go through, based on the importance of data to your business.
This enables you to get all of the benefits of an ML-powered logging solution at only a third of the cost and with more real-time analysis and alerting capabilities than before.
The TCO Optimizer allows you to assign different logging pipelines for each application/subsystem pair and log severity, giving you maximum control over your data. The priorities are described as follows:
|Low – Compliance Priority
Non-important log data that needs to be kept for
compliance/post-processing reasons will go
straight to your archive.
|Medium – Monitoring Priority
Logs that are used for monitoring or statistics will be
|High – Frequent search Priority
Your most important logs, typically high severity, or
You can always move your data from one level to another, even retroactively.
The TCO Optimizer displays the usage of all applications and subsystems, sorted by the top consumers. Click on any row to view the application/subsystem usage broken down by level of severity. You may use the top filters to easily locate a specific component.
With the drop-down menu on the right, you are assigning for each component its priority to determine the data pipeline the logs arriving from that subsystem will go through.
Low – Compliance Priority: Non-important log data that needs to be kept for compliance/post-processing reasons, will go straight to your archive.
Medium – Monitoring Priority: Logs that are used for monitoring or statistics will be fully available for those use cases by allowing you to define alerts, build dashboards, view statistics, query the live data stream, and receive proactive anomalies.
High – Frequent search Priority: Your most important logs, typically high severity, or business-critical data will be stored on highly available SSDs, replicated, and ready to be queried within seconds.
Block Priority: Non-important log data you do not wish to store at all, not even in your archive.
Also, you can assign different logging pipelines for different severities of a specific application-subsystem pair. Click on the arrow sign on the right of each line to see a breakdown of your logs by severity. This allows you to decide on your priority for this severity. The main drop-down will automatically show Multiple to respect your multiple selections.
If you wish to change the priority of some of your logs, you can always amend your original selections. This allows you to try out lots of different configurations to find the perfect optimization for your log analytics. This unlocks greater visibility of problems, shorter troubleshooting times, and finely tuned logging costs that will scale with your needs.