It is now possible to embed Azure Data Explorer dashboards in 3rd party apps. This comes on top of allowing embedding of the Monaco editor in 3rd party apps.
Dashboard embedding allows you to easily share data with your customers in a way that allows them to interact and explore it.
Using the various feature flags, you can control the exact controls that will be part of the embedded dashboard experience. For example, you can decide to remove the share, and add connection menu items or others.
Funnel is the latest visual type we added to Azure Data Explorer dashboards following the feedback we have been getting from customers. Funnel is usually used to track sequential flows to analyze attrition from stage to stage.
The status bar of a query results grid displays a few data points for selected cells in the grid, for example:
We are now also supporting Time Diff (in days) for Datetime data:
Close a single tab
We recently introduced a way to close all query tabs in a single click in the tabs list drop down:
To further improve efficiency, we added a Close button next to each tab name on the list, to allow you to close selected query tabs:
.Net and Node.js support in Sample App Generator
The sample app generator is a tool that allows you to create a working app to ingest and query your data in your preferred programming language. You can use this generated code as a baseline to write your own apps, altering the code as you go, or you can copy sections of the code into your own apps. The code includes comments with tips, best practices, links to reference material, and recommended TODO changes when adapting the code to your needs learn more
Starting today, generating sample apps in .Net and Node.js is supported along with the previously available options – Java & Python. Give it a try.
Simplifying JSON selection
Azure Data Explorer supports two JSON file formats:
json: Line separated JSON. Each line in the input data has exactly one JSON record. For more information, see JSON Lines.
multijson: Multi-lined JSON. The parser ignores the line separators and reads a record from the previous position to the end of a valid JSON.
Multijson is the recommended way to ingest data in ADX. To simplify this selection from UX, we will default the JSON data format to multijson in ADX. If users still wish to override this behavior, and fall back to json, they can check the “Ignore data format errors” box to proceed.