Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Azure Time Series Insights

Azure Time Series Insights is an end-to-end Platform-As-A-Service offering to ingest, process, store, and query highly contextualized, time-series-optimized IoT-scale data that’s ideal for ad-hoc data exploration, as well as operational analysis. Azure TSI is a uniquely extensible and customized service offering that meets the broad needs of industrial IoT deployments.

More details about the service are available Time Series Insights documentation.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add sorting capabilities to GetEvents API

    It seems the take parameter on the GetEvents API selects events at random, returning different responses for the same query.

    Adding the ability to sort by time (or another property) would make it easier to get the last 10 values that occurred, for example.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  3. Query aggregation of multiple series

    Allow the user to query aggregations across multiple series (predefined or even on demand).

    In our use-case we want to receive aggregations for the data of "sensor1 - sensor2" or "sensor1 + sensor2", as avg(), min(), max(), where min and max would show the highest sum of measured data of both sensors combined before aggregating.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  4. Retrieve markers added by users on charts

    It could be greate to be able to retrieve via API markers that analysts have spotted using Azure TSI, in order to persist and use those markers elsewhere.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add possibility to include multiple TimeSeriesId in request body or implement Json batch to have multiple requests in one.

    As I know current situation is that we can only ask for one timeseriesId in one request. It would be great to have possibility to put multiple timeSeriesIds in one request (some kind of grouping) or add possibility to have json batch functionality.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  6. Time Series Exploper - should be embeaddable.

    TSI - Explorer should be able to be embedded in a web dashboard the same way as PowerBI Embedded

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time Series Explorer UX - Analytics  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add data de-duplication and upsert

    Time Series Insights doesn't have a de-duplication feature. Today duplicates are just stored in TSI and that makes the query results wrong. We have the need for de-duplication and also upsert to replace or enrich existing time series.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Data ingestion  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add feature to send event for new ID (new instance) in TSI.

    I'd like to have an option to send an information for other resources that new instance (new sensor in my case) has been added to TSI. Maybe just a simple ServiceBus/EventHub hook or whatever queue.

    As it is right now all I can do is manually call Instances API with path = null in request body and check for instances without hierarchy since I always assign it for my known sensors. That's overly complicated and not really the right way.

    Just as TSI can be hooked to IotHub/EventHub as data source, there should be an option for output to a…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data storage  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to set custom interval size

    Currently interval size choices are set by TSI. an ability to input the desired interval size would be useful

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Fix search span and interval misalignment issue in AggregateSeries queries

    When aggregating data in TSI, you must provide an interval and a search span.

    Sometimes the intervals start before the search span instead of at the specified "from" time. This also results in inconsistent number of intervals being returned.

    e.g.

    "aggregateSeries": {

        "interval": "P1M",
    
    "searchSpan": {
    "from": "2020-11-01T00:00:00Z",
    "to": "2020-12-31T23:59:59.999Z"
    },
    ....

    }

    TSI returned 3 intervals with timestamps:

    - "2020-10-03T00:00:00Z"
    - "2020-11-02T00:00:00Z"
    - "2020-12-02T00:00:00Z"

    We expect 2 intervals with timestamps:
    - "2020-11-01T00:00:00Z"
    - "2020-12-01T00:00:00Z"
    | |

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  11. Increase maximum number of concurrent connections per environment

    Currently, only 20 concurrent connections are allowed which limits usage of the API heavily. Would be great if this was increased to a larger amount per environment.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add abillity to remove events within a given time period or with given time series Id

    There are no good ways to remove data from TSI, especially during development its a pain to recreate TSI's because you can't go back and change data and if you rerun the datasets you get duplicate datapoints, at the very least an update feature should be present that is based on the event time.

    59 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Data ingestion  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add ability to create "default" hierarchy and to populate new instances with dynamic values with formula

    Give ability to select a hierarchy by default and to specify a dynamic value to populate the instance on creation. ($event.client for example)

    When TSI receive a new message with unknown time-series id, the new instance use the default hierarchy, search the values with formulas and set the values

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series model  ·  Flag idea as inappropriate…  ·  Admin →
  14. DayOfWeek in DateTime Functions

    You can get the monthOfYear and the dayOfMonth but not the dayOfWeek. For our requirements it would be very helpful to have this possibility.

    Example
    We need only the days from monday to friday, within a daterange greater than x months.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  15. Apache Kafka as an event source to Time Series Insights

    I would like to use an existing Kafka stream to get data into Azure Time Series Insights, but the only event sources are Event Hubs or IoT Hub. Adding support for open-source such as Apache Kafka, Rabbit MQ, Active MQ, etc. would enable a lot of different scenarios.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Data ingestion  ·  Flag idea as inappropriate…  ·  Admin →
  16. The median aggregate returns null-aggregates when using "value": {"tsx": 'coalesce(toDouble($event.value.Long), $event.value.Double)'}

    See two examples of the payload when querying for a median aggregate below.

    Median2 works fine if Median1 is not in the payload. However if you try querying both (or only Median1) only null values are returned. I believe there is a problem using the coalesce function. This is not a problem if other aggregates are queried, such as min, avg, last, etc.

    "inlineVariables": {

            "Median1": {
    
    "kind": "numeric",
    "value": {"tsx": 'coalesce(toDouble($event.value.Long), $event.value.Double)'},
    "filter": null,
    "aggregation": {
    "tsx": "median($value)"
    },
    },
    "Median2": {
    "kind": "numeric",
    "value": {"tsx": '$event.value.Double'},
    "filter": null,
    "aggregation": {
    "tsx": "median($value)"
    },
    },
    },

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  17. Increase the number of variables that are possible per type

    Currently we have a customer with devices that have 260+ variables. When configuring these types i encoutered the problem that this can only be 50 variables per type. i would request that this number will be raised to 500 or more.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time Series Explorer UX - Model management  ·  Flag idea as inappropriate…  ·  Admin →
  18. Mode Aggregate function with Time Series Insights

    We have a requirement to aggregate data using MODE function ( returns the most occurring value from the given time range. Does Azure TSI supports this? Please suggest.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  19. 13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Time series query API  ·  Flag idea as inappropriate…  ·  Admin →
  20. Use instance fields for calculations

    Can we use the instance fields to calculate variables for a given type? And if so, how?
    So far I only see event data being used ($event.[value].double), but what if I need a static value?
    Something like $instance.[fieldname].Double would help but it doesn't seem to work like that...

    Git issue: https://github.com/MicrosoftDocs/azure-docs/issues/49367

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Feedback and Knowledge Base