For C# users, a NuGet package should be made available for working with the TSI Query API.
There is some code already here: https://github.com/Azure-Samples/Azure-Time-Series-Insights/tree/master/csharp-tsi-preview-sample/DataPlaneClient/Generated16 votes
The existing libs were based on internal usage, we’re excited to share some dedicated C# SDK work we’ve been working on to get your inputs. Please try it out and keep us posted with feedback. Thank you!
Chris Novak [MSFT] TSI PM Lead.
Downloading events from TSI is currently limited to 10000 events. This is probably because the query API is limited to 10000 events per query. Please consider increasing this limit.14 votes
It is currently not possible to do "group by" queries in TSI Gen 2 although it was possible in Gen 1 (https://docs.microsoft.com/en-us/rest/api/time-series-insights/gen1-query-api#get-environment-aggregates-api).
This seemed to be on the roadmap (fleet queries) but it should be proritized to allow migration between Gen1 and Gen2.13 votes
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
This is an area we’re currently investigating. We’d love to get more input on the scenario. And are evaluating the scope of the feature that folks would like. Please let us know if just single point retrieval suffices or if there’s interest in multi point temporal selection of a specific assets time series data and what you’d like to use the feature for as part of your analysis i.e. simplified API consumption , ML training etc.
Looking forward to hearing from you all! Please share your ideas on uservoice so others can join in.
Chris Novak [MSFT] TSI PM Lead.
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.9 votes
You can get the monthOfYear and the dayOfMonth but not the dayOfWeek. For our requirements it would be very helpful to have this possibility.
We need only the days from monday to friday, within a daterange greater than x months.5 votes
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.4 votes
The timestamp is an important factor in the Azure Time Series Insights. But there is no proper documentation regarding the format, the best practices to send timestamp in UTC (or in any other format) from the IoT device. It will be extremely helpful if there is proper documentation for this scenario.4 votes
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.3 votes
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
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.2 votes
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.
TSI returned 3 intervals with timestamps:
We expect 2 intervals with timestamps:
| |2 votes
- Don't see your idea?