Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 68526200D4C for ; Thu, 30 Nov 2017 15:19:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 66BA1160C04; Thu, 30 Nov 2017 14:19:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AE5A6160BEA for ; Thu, 30 Nov 2017 15:19:04 +0100 (CET) Received: (qmail 15242 invoked by uid 500); 30 Nov 2017 14:19:03 -0000 Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mesos.apache.org Delivered-To: mailing list issues@mesos.apache.org Received: (qmail 15228 invoked by uid 99); 30 Nov 2017 14:19:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Nov 2017 14:19:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E28E918082F for ; Thu, 30 Nov 2017 14:19:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 0wDe4KZJUWYL for ; Thu, 30 Nov 2017 14:19:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 5B92F5F39D for ; Thu, 30 Nov 2017 14:19:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D8A7CE0EFA for ; Thu, 30 Nov 2017 14:19:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8D4C62105A for ; Thu, 30 Nov 2017 14:19:00 +0000 (UTC) Date: Thu, 30 Nov 2017 14:19:00 +0000 (UTC) From: "Marc LeBourdais (JIRA)" To: issues@mesos.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MESOS-6003) Add logging module for logging to an external program MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 30 Nov 2017 14:19:05 -0000 [ https://issues.apache.org/jira/browse/MESOS-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272711#comment-16272711 ] Marc LeBourdais commented on MESOS-6003: ---------------------------------------- [~wrouesnel] I second [~wjoel]'s request. We're using Mesos at DigitalOcean and using the external container logger module to configure container logging to the local syslog socket on each Mesos host to be aggregated and centralized. In order to keep up to date with Mesos 1.3 and 1.4, we've made a couple new releases in our fork: https://github.com/digitalocean/mesos-external-container-logger/releases I'd rather not take over "maintaining" this module, but as long as we're still following the upgrades to Mesos, we'll likely keep updating the module unless it ends up getting merged (the ideal scenario). > Add logging module for logging to an external program > ----------------------------------------------------- > > Key: MESOS-6003 > URL: https://issues.apache.org/jira/browse/MESOS-6003 > Project: Mesos > Issue Type: Improvement > Components: modules > Reporter: Will Rouesnel > Assignee: Will Rouesnel > Priority: Minor > > In the vein of the logrotate module for logging, there should be a similar module which provides support for logging to an arbitrary log handling program, with suitable task metadata provided by environment variables or command line arguments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)