You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In other datasources we often have a pattern where users can select to have their data formatted as a Table or as a Time Series
Here's Postgres and Athena for example:
This is particularly useful for sql datasources as data often by default comes back in a long format and our Alerting feature only works with wide format time series. When users select "format as timeseries" in other datasources, we also convert this to a wide time series, which could make it possible to alert on data from open search more easily. It also could be helpful in selecting the correct visualization when in the explore mode.
Describe the solution you'd like
I think it would be good to do a little bit more research in how to implement this with a design doc and also double check should we implement this in the first place. If this ends up being a bad plan, I think we should still figure out a workaround for use cases like this: #360
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In other datasources we often have a pattern where users can select to have their data formatted as a Table or as a Time Series
Here's Postgres and Athena for example:
This is particularly useful for sql datasources as data often by default comes back in a long format and our Alerting feature only works with wide format time series. When users select "format as timeseries" in other datasources, we also convert this to a wide time series, which could make it possible to alert on data from open search more easily. It also could be helpful in selecting the correct visualization when in the explore mode.
Describe the solution you'd like
I think it would be good to do a little bit more research in how to implement this with a design doc and also double check should we implement this in the first place. If this ends up being a bad plan, I think we should still figure out a workaround for use cases like this: #360
The text was updated successfully, but these errors were encountered: