It would be convenient if jmyapi assisted making interval queries that don't wholly exist in a single archiver deployment. For example the ops deployment has the most current data. However, that may age out as early as 9 months. The history deployment usually lags the ops deployment by a few months. There is overlap. But if you wanted an interval that includes the most recent and goes back further than 9 months (or whatever the ops age out threshold is) then you must make two separate queries and "stitch" them together. Maybe jmyapi can help here?
It would be convenient if jmyapi assisted making interval queries that don't wholly exist in a single archiver deployment. For example the ops deployment has the most current data. However, that may age out as early as 9 months. The history deployment usually lags the ops deployment by a few months. There is overlap. But if you wanted an interval that includes the most recent and goes back further than 9 months (or whatever the ops age out threshold is) then you must make two separate queries and "stitch" them together. Maybe jmyapi can help here?