Introduction to Drata Visualizations - maneeshpal/Drata GitHub Wiki
Most of he conventional visualization tools are built along the lines of visualizing something by default based on the data you are tracking, and then lets users apply rules and switch visualizations. There is nothing wrong with that approach, but it leaves less room for building visualization with intelligent data segmentation and aggregations.
Drata takes a different approach though. You may notice that Drata needs you to specify the kind of visualization upfront, rather than giving you the ability to switch post widget creation.
This is because, Drata expects different format for linechart, areachart and Trend chart as opposed to Pie and bar charts. This hard set fundamental distinction lets Drata segment the data more efficiently geared towards providing useful visualizations, and not dumb and beautiful charts.
For example, in line chart, when you group data by a property, Drata will visualize each group as its own line, whereas in Pie/Bar charts, Drata will perform aggregations based on your selections and groupings; resulting in a visualization that best suit the user's requirements.
Don't get me wrong, but Linechart and Area charts does have the ability to aggregate data. Its done using the property you select as your x-axis. When you group a date property on x-axis by a specific interval, it will result in timeseries chart.

The changes you make to any of the widget view options detailed in the above figure will persist those changes immediately. So, you don't need to edit the widget in order to save these changes.

- Depending on how you built your query using widget editor, the resulting data could resolve to multiple groups. This label is an index to those groups.
- In the above figure, we are dealing with line chart. So this column resolves to x-axis in the chart.
- This is value being visualized on y-axis.
Checkout how to