From owner-freebsd-cloud@freebsd.org Wed Aug 30 23:39:30 2017 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10BD3E0CC4B for ; Wed, 30 Aug 2017 23:39:30 +0000 (UTC) (envelope-from raf@rafal.net) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFCCA84BC4 for ; Wed, 30 Aug 2017 23:39:29 +0000 (UTC) (envelope-from raf@rafal.net) Received: from [192.168.40.37] (unknown [86.40.118.125]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id C75C4509B8; Wed, 30 Aug 2017 19:39:27 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: AWS CloudWatch Logs Agent From: Rafal Lukawiecki In-Reply-To: <084bd6ad-9ffd-c097-1d46-c8cb41d745ee@nomadlogic.org> Date: Thu, 31 Aug 2017 00:39:26 +0100 Cc: freebsd-cloud@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0A93F7FC-5547-4A67-B3D9-BB59027FDAD6@rafal.net> References: <4FFC6F3B-E8A1-49EE-A05A-C6B9B0A615FF@rafal.net> <0100015e3565144c-18dc3e52-fcba-4b30-bf2f-58b99b55562d-000000@email.amazonses.com> <456A3074-08D2-4141-81EF-5CD6B1B53899@rafal.net> <084bd6ad-9ffd-c097-1d46-c8cb41d745ee@nomadlogic.org> To: Pete Wright X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 23:39:30 -0000 Dear Pete, that was my feeling too=E2=80=94I suspect that for someone = more skilled than me in FreeBSD rc.d it should be realistically possible = to port it, but the spaghetti nature of the awslogs script would also be = something to contend with. I did a bit of searching, but the only = reference to awslogs that I found on GH is this one: https://github.com/jorgebastida/awslogs While this looks like a good utility for CloudWatch Logs querying, it = does not seem to deal with the agent and actual log collection. The AWS = GitHub account does not seem to list anything related amongst their 70+ = repositories... If you embark on such a port, I would be happy to test, help, and give = feedback. On the other hand, please let me know if you find anything = else that could be of use. Many thanks. Rafal -- Rafal Lukawiecki Data Scientist and Director=20 Project Botticelli Ltd > On 31 Aug 2017, at 00:28, Pete Wright wrote: >=20 >=20 >=20 > On 08/30/2017 16:19, Rafal Lukawiecki wrote: >>=20 >> As for the CW Logs, unfortunately the script at curl = https://s3.amazonaws.com/aws-cloudwatch/downloads/latest/awslogs-agent-set= up.py is a bit too daunting for me to try rewriting using my brand-new = rc.d scripting skills, with only a hundred lines working (!) so far = behind my belt. >=20 > hi rafal - i also took a look at that python setup script. >=20 > my initial impression was that is was full of linux'isms (the first = line being #!/usr/bin/python being the first thing i noticed). and = while a lot of the setup code is linux specific, i think there are some = bits in there which could be ported to freebsd. do you happen to know = if there is a git or other open-source repository available with the = awslogs-agent code out there? i didn't find anything after a quick = google search. >=20 > cheers, > -pete >=20 > --=20 > Pete Wright > pete@nomadlogic.org > @nomadlogicLA >=20 > _______________________________________________ > freebsd-cloud@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-cloud > To unsubscribe, send any mail to = "freebsd-cloud-unsubscribe@freebsd.org"