Log Management
Investigate and dig into log data with contextual insights.
Pay-As-You-Go
$0.4
per million traces events*
- Unified Log Management
Consolidate logs from every source into one place for streamlined oversight. - Versatile Log Processing
Use 100+ built-in processing templates to standardize and parse diverse log formats for quick, targeted searches and actionable insights. - Log Correlation
Link logs across infrastructure, systems, and apps for both forward and backward trace queries. - Instant Anomaly Detection
Automatically spot unusual log patterns and group related data for rapid troubleshooting.
*Billed daily, the cost is based on data generated from logs, events, security check, and synthetic tests.
Multi-Year/Volume Discounts Available
Common Questions
- Are there any other data types billed alongside log data?
Yes, there are three types of data billed in the logic of log data:
- Enabling log data collection via DataKit and reporting it to the Truewatch Platform.
- Activating monitoring, intelligent monitoring, SLOs, or reporting custom events via OpenAPI to Truewatch Platform.
- Initiating Synthetic testing
- How is the log volume calculated?
- Log volume is measured by aggregating the number of new log entries generated hourly. This includes all logs collected and reported from various sources, ensuring a complete view of your system's log activity.
- Are there any additional billing items involved in processing and analyzing log data?
- Yes, you may also need to utilize the central pipeline for log data processing and governance, which could incur additional costs depending on your usage. For more details, please contact us.
- Why is billing based on the number of log events instead of the actual log data volume?
- Truewatch is not just about log storage—it’s a powerful data analysis platform. Billing based on the number of log events rather than the actual log data volume allows users to focus on meaningful insights rather than raw data size. This approach ensures fair pricing by aligning costs with actionable events.
- How does billing work when changing the data storage period?
- When you adjust the data storgae period, data generated before the adjustment will continue to follow the previous storage policy for billing purposes. Data generated after the change will be indexed and billed according to the new storage policy. For example, if you reduce the retention period from 14 days to 7 days, data before the adjustment will follow the 14-day policy, while data afterward will use the 7-day policy.