Closed Bug 1111754 Opened 11 years ago Closed 9 years ago

Use syslog in cloud-tools

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rail, Unassigned)

Details

Attachments

(1 file)

* forward all logs to localhost's syslog * localhost should also forward them to some other place to aggregate them
Attachment #8537979 - Flags: review?(dustin)
Comment on attachment 8537979 [details] [diff] [review] cloud-tools-syslog-puppet.diff Review of attachment 8537979 [details] [diff] [review]: ----------------------------------------------------------------- ::: modules/aws_manager/templates/aws-secrets.json.erb @@ +14,5 @@ > +# to use local syslog > + > +if scope.function_secret(["aws_manager_syslog_address"]) != '' -%> > + "syslog_address": <%= scope.function_secret(["aws_manager_syslog_address"]) %>, > +<% end -%> I don't think tihs needs to be a secret - just a config var. In bug 1066145 I introduced a generic $log_aggregator config variable, which you could use here. I have a patch on that bug to back out the definition of that variable, so please comment there and f- the patch if you do use the variable.
Attachment #8537979 - Flags: review?(dustin) → review-
It's kind of secret, we are going to use papertrail to send logs to, and the destination is sikrit there.
Let's load the secret in the config, then.
I haven't been working on this for a while. Back to the pool
Assignee: rail → nobody
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: