Log retension for 90 days in Octopus

Legacy Execution
1

we are planning for an upgrade activity.And we have a requirement of tracking the log for 90 days.So please help us in this.

Thanks & Regards ,
Dhivya P

3

Hi,

Thanks for getting in touch. Can you let me know a little more about your requirements? For example, do you mean the Octopus server logs, or task logs from deployments?

Looking forward to helping you,
Michael

4

Hi ,
it would be great if we could track both the logs.

5

Hi ,

It would be great if we could track both the logs.

Thanks & Regards,

Dhivya P

6

Hi,

Deployment logs are stored as task logs in Octopus. Along with deployment artifacts, records of releases and deployments, task logs are controlled by retention policies that determine when, if ever, to delete. You can read more about retention policies here and you may also want to read about lifecycles here.

Octopus server logs contain some information about transactions, api calls, connections to the server, configuration changes etc. There’s no deployment data in there. That logging is controlled by an Nlog configuration (see here), so you should be able to edit the config to achieve retention as per your needs (e.g. https://github.com/nlog/NLog/wiki/File-target#one-log-file-per-day).

Hope that helps. If not, get back to me.

Michael

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.