Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retention policies/Continuous queries - common solutions (Influxdb) #544

Open
psyciknz opened this issue Apr 13, 2023 · 3 comments
Open
Labels
docs Documentation request or update

Comments

@psyciknz
Copy link

I guess similar to #259
Are thhere any common continuous queries and retrention policy setups that can be shared documented? I have CQs on clients and some of the other tables. But after turning on DPI I noticed a space blow out in my influxdb. And was curious if there were some base CQs people had worked out, that could be added to the documentation. To help people manage space.

That or the ability to assign a single measurement to a different retention policy. Ie ClientDPI to a 30 day retention policy rather than use the database default autogen.

@platinummonkey
Copy link
Contributor

This would be specific to the output source. This question seems to be focused on influxdb

@psyciknz psyciknz changed the title Retention policies/Continuous queries - common solutions Retention policies/Continuous queries - common solutions (Influxdb) Apr 14, 2023
@psyciknz
Copy link
Author

Yes, it is specific to iinflux.
I've updated the title to reflect that. But I believe the questions still stand.

@platinummonkey platinummonkey added the enhancement New feature or request label Aug 9, 2023
@davidnewhall davidnewhall added docs Documentation request or update and removed enhancement New feature or request labels Apr 25, 2024
@platinummonkey
Copy link
Contributor

perhaps https://community.influxdata.com/t/how-to-create-a-retention-policy-for-measurement/21190 answers your question?

I imagine the duration depends on:

  • How much storage space each deployment would have
  • How long they need to keep it for any contractual reason
  • How much they are willing to keep paying for storage and maintenance costs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation request or update
Projects
None yet
Development

No branches or pull requests

3 participants