InfluxDB UI vs Chronograf (and Kapacitor)

Hi, guys!

I’m new to influx db stack, so let me ask some questions. I was playing with influx db UI so far, I’ve built some dashboards using telegraf plugins for system and docker metrics. They look like this in influx db UI:

I really like them! But moving forward with TICK stack I’ve realized that there is a separate Chronograf application and having it installed I’ve discovered something similar (yeah it looks like it is something that has extra functionality than influx db UI). But I was able to create the same dashboards (the only difference, now it uses influxQL instead of Flux by default. And it looks like this:

Which looks similar, but different. And TBH I like these dashboards UI less.
First of all, I’d like to understand does influx db UI uses Chronograf under the hood or it is a completely separate code/dashboards UI?
Because my second question - if it is possible to make Chronograf graphs to look exactly the same? Maybe there is a theme or some other settings to achieve that?

Second part of my question is similar but related to the alerts/tasks we can create in influx DB UI and Kapacitor application. It looks like there is similar duplication of functionality, but the latter one has more extended features.

Basically, I just wanted to understand better the architecture of TICK stack and what are the features of each element of TICK stack and its zones of responsibility. Thanks in advance!

Is there anyone who knows the answer?

Hello @khataev,
In v2 chronograf and a kapacitor alternative was just merged into into a single product instead of having them be separate.
So v1 had TICK:
T = data collection
I = the database
C = the UI
K = data processing engine

V2 is all just combined together but instead of using TICK scripts for kapacitor and influxql for querying you use Flux for querying and creating data processing tasks. This was all done to simplify the product.

However we’re now on v3 of InfluxDB.
v3 doesn’t have TICK scripts or kapacitor or Flux. It uses SQL for querying (and influxql if you want) and focuses on interoperability so you can use other purpose built tools for data processing, etl, and data visualization.
InfluxDB 3.0 is up to 45x Faster for Recent Data Compared to InfluxDB Open Source | InfluxData.
Use Tableau to query and visualize data | InfluxDB Cloud Dedicated Documentation for Tasks with InfluxDB | InfluxData

I shared the benchmark and some examples to give you an idea of where things are headed so you can make a better decision about how you want to invest your time.

@Anaisdg thank you very much for detailed explanation!

v3 doesn’t have TICK … and focuses on interoperability so you can use other purpose built tools for data processing, etl, and data visualization.

does that mean that in v3 OSS there is no more Chronograph UI and its charts? Do you have information when v3 OSS version will be released approximately?

@Anaisdg can you please give some insights on Chronograf’s related plans in 3.0 (it wasn’t touched in the article you attached)? Will it still be part of Influx Edge/Community? Or we should start looking into something like Grafana?