Since remote_read offers poor performance for querying data and promscale can be queried directly as well as use prometheus alerts there seem to be no reason to configure this option. This is potentially a breaking change for some user so I am bumping major version as well as putting upgrade path information.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
What this PR does / why we need it
Since
remote_readoffers poor performance for querying data and promscale can be queried directly as well as use prometheus alerts there seem to be no reason to configure this option. This is potentially a breaking change for some user so I am bumping major version as well as putting upgrade path information.Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged)Special notes for your reviewer
Checklist