Before you do that…
120 seconds is still an issue for a 30 day span in any database. You should be getting subseconds speed if not few seconds only with some finetuning.
Next step is vetting your influxdb schema design and the use of the contains filter
The rule with influxdb is as follows:
measurement and tags are indexed whereas fields are not.
So you may want to configure object as a tag (if not already) since you are filtering on it
The other issues you will need to tackle is the use of contains which is notorious for performance issues in any query language. Other alternatives are found in this post
So once you have done your due diligence with best practices on the influx schema side of things and using something other than contains function, you can then confidently create a bug for increasing timeouts