You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Time Series engine is an experimental way of storing metrics. I believe it was heavily influenced by the Prometheus use case. The docs have more info than me on the actual implementation/usage.
Considering it's experimental, I would say the current exporter's metrics tables are relatively more stable. I expect the new engine will be improved over time however, and may eventually be superior to the current exporter's schema.
For now it's best to use the tables that are provided, even better if you modify the schema to fit your needs. If you wanted to experiment with the Time Series engine you may be able to set up some kind of materialized view to re-structure the data into a new table
The Time Series engine is an experimental way of storing metrics. I believe it was heavily influenced by the Prometheus use case. The docs have more info than me on the actual implementation/usage.
Considering it's experimental, I would say the current exporter's metrics tables are relatively more stable. I expect the new engine will be improved over time however, and may eventually be superior to the current exporter's schema.
For now it's best to use the tables that are provided, even better if you modify the schema to fit your needs. If you wanted to experiment with the Time Series engine you may be able to set up some kind of materialized view to re-structure the data into a new table
Component(s)
exporter/clickhouse
Describe the issue you're reporting
What are the differences between the metric table structure of the ClickHouse Exporter and the structure provided by ClickHouse officially? https://clickhouse.com/docs/en/engines/table-engines/special/time_series
Which is better?
The text was updated successfully, but these errors were encountered: