----- Original Message ----- > From: "Den Cowboy" <[email protected]> > To: "Jeff Cantrill" <[email protected]> > Cc: [email protected] > Sent: Wednesday, 23 November, 2016 9:48:17 AM > Subject: Re: Clean logs in ES on Origin 1.2.0 > > > > Is there also some solution for the cassandra DB for the metrics?
For metrics, the data in Cassandra is configured to be deleted after a certain time period. By default this is 7 days, but its configurable: https://github.com/mwringe/openshift-ansible/blob/master/roles/openshift_hosted_templates/files/v1.2/enterprise/metrics-deployer.yaml#L120 For capacity planning, it should be similar to what we have for 1.3: https://docs.openshift.org/latest/install_config/cluster_metrics.html#capacity-planning-for-openshift-metrics > > Van: [email protected] > <[email protected]> namens Den Cowboy > <[email protected]> > Verzonden: woensdag 23 november 2016 10:40:08 > Aan: Jeff Cantrill > CC: [email protected] > Onderwerp: Re: Clean logs in ES on Origin 1.2.0 > > > Thanks, as fastest solution at the moment, I've updated the dc's of the > curator. > Will check in a couple of days if it's working. > > Van: Jeff Cantrill <[email protected]> > Verzonden: dinsdag 22 november 2016 14:52:57 > Aan: Den Cowboy > CC: [email protected] > Onderwerp: Re: Clean logs in ES on Origin 1.2.0 > You can create a secret with a file that has content like: > > .defaults: > delete: > days: 7 > runhour: 0 > runminute: 0 > and add the volume to the deployment config as described here: > https://github.com/openshift/origin-aggregated-logging/tree/v1.2.0#curator > > Alternatively, if you do not provide the secret, you could update the > following value in the deploymentconfig: > https://github.com/openshift/origin-aggregated-logging/blob/v1.2.0/deployment/templates/curator.yaml#L90 > > > > https://github.com/openshift/origin-aggregated-logging/tree/v1.2.0 > > On Tue, Nov 22, 2016 at 9:34 AM, Den Cowboy < [email protected] > wrote: > > > > > > Hi, > > > > > We have an origin 1.2.0 cluster in which we've integrated the logging > project. It works fine but we just followed the setup tutorial. We don't > know may about the real setup. > > > > > > We're facing sometimes issues that our disk is getting too fill because our > ES is keeping to many data. > > How can we easily configure the curator to delete every log of every project > once a week? > > > We took a look to the documentation: > > > myapp-dev: > delete: > days: 1 > > myapp-qe: > delete: > weeks: 1 > > .operations: > delete: > weeks: 8 > > .defaults: > delete: > days: 30 > runhour: 0 > runminute: 0 > But it isn't clear for us. Isn't there just a setting in the deploymentconfig > or what's the most easy approach for this? > > > > > > > Thanks > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > > > > -- > -- > Jeff Cantrill > Senior Software Engineer, Red Hat Engineering > OpenShift Integration Services > Red Hat, Inc. > Office : 703-748-4420 | 866-546-8970 ext. 8162420 > [email protected] > http://www.redhat.com > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
