Azure Data Explorer

  1. Provide out of the box resource governance for Kusto clusters

    Our Kusto cluster is used for production site and tools and needs to have 99.99% availability. However, as our cluster is open to tens of thousands of users across the company for ad-hoc queries, we often suffer from unexpected cluster wide outages due to misbehaved customers. We have tried both cluster-wide query limits as well as customized approaches, however, neither is helping us much. We would like to see Kusto to provide the resource governance solution out of box.

    31 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add ".update" management command to allow correct wrong ingested data

    When data gets wrongly ingested into ADX, it very hard to correct this data afterwards. -> I know ADX is a append-only store.

    Let's say a sending machine had issues with daylight saving time and all data is shifted and after some days, it gets recognized and the machine is sending correct values. There is small slice of data, which needs to be aligned.

    Or some properties where wrongly set over some time. Same as above.

    Currently, we use the ".purge" command and re-ingest the data, which leads to a wrong "ingestion-time". Another option is completely re-ingest the data into…

    14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add something like ingestion_time() for follower databases

    Our data pipeline is very sensitive to how long it takes data to arrive. The ingestion_time() feature is incredibly useful for understanding the distribution of ingestion delays for each table. Now that we're using follower databases more frequently, we don't have good insight into how long it takes for the data to be queryable from our follower database. It's something like ingestion_time() + metadataRefreshDuration... but there's no additional field that we can query to get that metadataRefreshDuration. Adding this information would give us a lot more ability to tune our pipeline to the characteristics of each situation.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. parse_ipv6

    The parse_ipv4() function works well for handling ipv4...but we also deal with a lot of ipv6. It would be very challenging to implement this correctly as in Kusto Query Language in an efficient way.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow creation of Tables & Data Maps in ARM template

    It doesn't make much sense that ARM template deploy of AzDEx allows for creation of Clusters, Databases, and DataConnections when DataConnections expliclity depend on a Table and DataMap to exist. In fact the error message is simply "Bad Input" with an "Internal Server Error" if somebody mistakenly tries to do this..

    DEx should be able to be fully-configurable via ARM including Tables and Datamaps so the existing capability of creating DataConnections via ARM is able to actually be used.

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Record tables accessed in .show queries

    I’d like to get a summary of table usage and query costs compared against extent size and ingest costs, for use in value vs. cost discussions and for targeting table or workflow optimizations.

    With “.show tables details” for extent size and “.show commands” for ingest costs, the only piece I am missing here is the ability to link information from .show queries to the tables that were accessed. I understand the text of each query is present, but parsing that to determine a list of tables accessed is nontrivial and becomes really problematic given the use of stored functions (which…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Enable deletion/drop of functions in Kusto.

    I want to wipe out all code in Kusto DB so that I can install new ones from source controls. The reason behind delete everything logic is I do not want unreferenced functions to exist if they are removed from source control repo.
    Enable deletion/drop of functions in Kusto.
    Better yet, allow Azure Data explorer Command in Azure Pipelines to drop multiple files

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. More datetime functions

    There are basic datetime manipulation functions, but there should be many more. For instance, make_datetime() modifies the format of a current datetime object, but there is no function to specify the format of a string that should be a datetime. So if the month and day are not in the expected order, the string can't be parsed. Additionally, the date functions assume that the dates are in UTC, rather than allowing the user to specify that a date is in another time zone. Time zone conversions that account for daylight savings time, etc are needed. It should have all of…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Permissions by views

    I would be useful to be able to restrict specific users to only be able to access data to a specific view
    (without direct access underlying tables). This could enable use to limit specific users access to time series data for a specific period or specific equipment.

    15 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Autoscale form 1 VM on Azure Data Explorer's Data Management cluster

    Autoscale form 1 VM on Azure Data Explorer's Data Management cluster

    6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Kusto explorer app: Ctrl+F in result view shall support search for "10:27:33"

    The search function (Ctrl+F) in the Kusto explorer desktop app shall support queries like "10:27:22" to ease search in log file like contents

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Mobile phone support

    1. Make the web UI work on Android Chrome as first priority
    2. When accessing from phone, adjust the UI to be suitable for small screen

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Include more node memory details for E_LOW_MEMORY_CONDITION errors.

    When a query or command fails with one of the E_LOW_MEMORY_CONDITION errors, please include information about the node's memory consumption at that point in time. How much was allocated to the current query, to other queries and commands, and how much was remaining available. I think it could help with the diagnostics of such errors.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. .show operation details with multiple operation ids

    Currently, if we do IngestionFromQuery operations using .set-or-append or .append like commands using async, we get the operation id to track the progress of the operation later on. We could get the status of multiple operations using .show operations command. But, we get the operation details of only one operation with .show operation details command. This makes us fire lot of .show operation details commands to track get the Ingestion time, rowcount of the ingested tables. It would be great if Kusto had capability to fire only one Command to get the operation details of mutliple operations like .show operation.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Create clone of a Kusto Database.

    I would like to have the capability of creating a clone of the database, where the newly created database is exactly the same as one it is cloned from (including permissions, folder structures of tables/functions, etc).

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Expose row counts and data size for ingestion command in .show command

    In.show commands result, show number of rows affected and data size affected, at least for ingestion command (like CommandType = DataIngestPull)

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Follow at the table level

    We love the database follower feature but it would be fantastic if we could follow at a table level.

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Mapping EventData properties during Event Hub ingestion

    When configuring a JSON Ingestion Mappings pre-created on a table, we couldn't map and access Properties which are set by Event Hub service in the EventData.SystemPropertiesCollection structure of each received message. These Properties are:
    • PartitionId
    • SequenceNumber
    • Offset
    • EnqueuedTimeUtc

    But also we could have to map any custom properties that we want to store in the same collection when sending messages to event hub.

    8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  19. In Kusto.Explorer default to showing query results instead of query summary

    In Kusto.Explorer, after querying, it always shows the "Query Summary" window, but I only care about the "Results" tab. If I try to close the query summary, it just comes back on the next query. And if I try to dual-pane the results and query summary, the layout is reset on next query.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Operation Text, Database to .show operations

    It would be useful to be able to see all currently running commands similarly to how we can see .show running queries. I have this query which shows me the currently running operations, but it does not have the level of detail that the .show commands query returns:

    .show operations
    | where StartedOn > ago(1h)
    | sort by LastUpdatedOn desc
    | summarize max(LastUpdatedOn), make_list(State) by RootActivityId, Operation
    | where list_State !contains "Completed" and list_State !contains "Failed"

    Specifically, it would be useful to see the database context in which the operation was running as well as the command text associated. The…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Azure Data Explorer

Categories

Feedback and Knowledge Base