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

R. Tyler Croy tyler at monkeypox.org
Fri Mar 17 15:32:02 UTC 2017


(replies inline)

On Fri, 17 Mar 2017, Olblak wrote:

> 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. 


This is not for logs of any importance, like error logs, this is only access
logs. For which we literally have *gigabytes* of access logs for abusive
traffic.


If you think access logs are that important, then I will make a Puppet change
to stop logging all redirect status codes for ci.jenkins.io




- 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
------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20170317/6eca6236/attachment.asc>


More information about the Jenkins-infra mailing list