Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=linux.ibm.com (client-ip=148.163.156.1; helo=mx0a-001b2d01.pphosted.com; envelope-from=mspinler@linux.ibm.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.ibm.com Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 44tF6S01gXzDqMr for ; Tue, 30 Apr 2019 05:27:27 +1000 (AEST) Received: from pps.filterd (m0098393.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3TJ6YMJ023069 for ; Mon, 29 Apr 2019 15:27:23 -0400 Received: from e17.ny.us.ibm.com (e17.ny.us.ibm.com [129.33.205.207]) by mx0a-001b2d01.pphosted.com with ESMTP id 2s65svukw4-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 29 Apr 2019 15:27:22 -0400 Received: from localhost by e17.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 29 Apr 2019 20:27:21 +0100 Received: from b01cxnp22033.gho.pok.ibm.com (9.57.198.23) by e17.ny.us.ibm.com (146.89.104.204) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Mon, 29 Apr 2019 20:27:20 +0100 Received: from b01ledav002.gho.pok.ibm.com (b01ledav002.gho.pok.ibm.com [9.57.199.107]) by b01cxnp22033.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x3TJQ45q32899154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Mon, 29 Apr 2019 19:26:04 GMT Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5E0B5124058 for ; Mon, 29 Apr 2019 19:26:04 +0000 (GMT) Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 40A8B124053 for ; Mon, 29 Apr 2019 19:26:04 +0000 (GMT) Received: from [9.10.99.36] (unknown [9.10.99.36]) by b01ledav002.gho.pok.ibm.com (Postfix) with ESMTP for ; Mon, 29 Apr 2019 19:26:04 +0000 (GMT) Subject: Re: phosphor-logging plugins vs new daemons To: openbmc@lists.ozlabs.org References: From: Matt Spinler Date: Mon, 29 Apr 2019 14:26:04 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-TM-AS-GCONF: 00 x-cbid: 19042919-0040-0000-0000-000004E8CF9F X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00011018; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000285; SDB=6.01196203; UDB=6.00627303; IPR=6.00977052; MB=3.00026652; MTD=3.00000008; XFM=3.00000015; UTC=2019-04-29 19:27:21 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19042919-0041-0000-0000-000008F4D257 Message-Id: <971a92ed-83f5-ec8d-c28d-aca9946245f3@linux.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-29_11:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904290129 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2019 19:27:28 -0000 On 4/25/2019 1:11 PM, Matt Spinler wrote: > Hi, > > We have some work coming up where we need to create different formats of > error logs based on the phosphor logging error log items that are > created. > We can accomplish this by either creating a separate daemon that listens > for D-Bus signals for new log entries, or we come up with a plugin > architecture for phosphor-log-manager where we let libs register > functions > in certain points, like before/after a log is created/deleted. > > At this point we are leaning toward the plugin route, as apparently > there was some discussion at the last OCP that recommended this. > > I'm just wondering if anyone has any leanings either way, or any other > ideas before we start on a design document? > I pushed up a short design that proposes using plugins at https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/21071 > Thanks! > Matt >