[receiver/sqlquery] Support of Start and Stop timestamp value Column #18925
Comments
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
The issue is still relevant. The proposed solution has been approved #19160 . Waiting for workflows. |
…19160) In this PR, support for Start and Stop Timestamp to be picked up from the metrics stored in the rows is added. This will allow SQL queries to be more expressive and allows users to define the period of aggregation which is not only dependent on the default system time set upon processing. **Link to tracking Issue:** #18925 #14146 --------- Co-authored-by: Juraci Paixão Kröhling <juraci.github@kroehling.de>
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Resolved #19160 |
Component(s)
receiver/sqlquery
Is your feature request related to a problem? Please describe.
Currently, the SQL query receiver can add the current timestamp to metrics. Adding support for optional starting and ending timestamp value columns would be helpful. This will allow users to put timestamp-based checks to retrieve values from the table with where conditions and set timestamp if provided. This avoids stale data fetch if queried at regular intervals.
Describe the solution you'd like
The start and stop timestamp fields can be added to metric cfg with corresponding checks.
StartTsColumn string mapstructure:"start_ts_column"StopTsColumn string mapstructure:"stop_ts_column"Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: