search

grafana / iot-sitewise-datasource

IoT Sitewise
Apache License 2.0
18 stars 10 forks source link

Feature request to add to query options List data stream alias #225

Open fridgepoet opened 1 year ago

fridgepoet commented 1 year ago

Discussed in https://github.com/grafana/iot-sitewise-datasource/discussions/186

Originally posted by **jhoulihan** May 15, 2023 Greetings, I would like to request the feature to add to Query Type: "List Data Stream Alias" . - The output to be tabular - similar to "List asset models" query. Could I suggest table headings of: property alias, last value, last value update, asset property name(if it exists), asset name(if it exists) , creation date. - A filter on the property alias should be applied before querying (I have ~20,000 datastreams and growing!) , ideally to allow for wildcards mid-string, eg /Plant1/Device1/+/PV/VALUE or /Plant1/Device1/++ - Some default dataset return limit eg 30 rows per page - to prevent performance degradation or similar - Create the ability to copy the property alias string to clipboard, to allow for pasting elsewhere. If possible, cater for selecting and copying data by the property alias column (ie select multiple rows in the property column) My sitewise/grafan solution uses OPC-UA data streams and not asset models to display timeseries, because it's faster to deploy timeseries data for endusers to consume and enjoy the hardwork the Grafana iot sitewise datasource team have put in :-) - the feature would be a great capability to allow endusers to develop their own dashboards by simply using the list of property aliases with the convenience of this query to look up what data streams they require.
tracy-french commented 8 months ago

This could be partially implemented by creating a query for ListTimeSeries (https://docs.aws.amazon.com/iot-sitewise/latest/APIReference/API_ListTimeSeries.html) and exposing the timeSeriesType filter to pass in "DISASSOCIATED".

Including the latest value in the query result requires additional API requests. Could we separate the requirement to list the latest values and reuse the existing "Get Property Value" query?