[Jenkins-infra] Proposal: only keep last 24h of ci.jenkins.io access logs

Olblak me at olblak.com
Fri Mar 17 09:20:29 UTC 2017


Would it possible to send those logs on a blob storage or any other
servers with enough spaces?
Because 24h can be a too short period of time.
Between the moment an error occurs, it's detected, someone start to
investigate at it.
You may miss important information.
I would keep logs at least few days. 

-- 
  Olblak

On Thu, Mar 16, 2017, at 07:42 PM, R. Tyler Croy wrote:
> I have fielded a few more alerts than usual with ci.jenkins.io disk
> filling up
> due to excessive access logs caused by the numerous abusive build
> monitors and
> scripts that point to ci.jenkins.io by default (see:
> https://jenkins.io/infra/ci-redirects/)
> 
> In a 24 hour period we'll create in excess of 1-2GB of access logs for
> this
> garbage traffic alone.
> 
> 
> I don't think the access logs for ci.jeknins.io are of any use, and would
> like
> to simply delete old access logs after one day. Retaining 24 hours for
> debugging purposes if necessary.
> 
> 
> What are your thoughts? Any compelling reason to store these logs?
> 
> Cheers
> - R. Tyler Croy
> 
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>      xmpp: rtyler at jabber.org
> 
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> ------------------------------------------------------
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)


More information about the Jenkins-infra mailing list