From nobody Mon May 29 10:41:38 2023 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QVBsm29Njz4XYHH for ; Mon, 29 May 2023 10:41:48 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QVBsm0FHXz4SDb for ; Mon, 29 May 2023 10:41:47 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; none Received: from [192.168.147.11] (host-95-253-59-10.business.telecomitalia.it [95.253.59.10]) (authenticated bits=0) by soth.netfence.it (8.17.1/8.17.1) with ESMTPSA id 34TAfcfn046263 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 29 May 2023 12:41:39 +0200 (CEST) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202304; t=1685356906; bh=sVxMh6E5SJarZTakx0CTpzXU6U2imZfn6EBEEmTB4jI=; h=Date:Subject:To:References:From:In-Reply-To; b=JJI1QmEen8GVchCHQj2K12Rk0dO90R0i68Z2e0QZlKwJSz3VBCyRW4GXQAZTK6vfx t6SQtU3ixfkFc0P42JnhyZtzMLub3pzrCnpMo3uWymelmFZQl0vNVXes+kPwzxn9u9 ydZGwL9DlQoipAydJ1uH31A3W4uFGu5mITdnzBNU= X-Authentication-Warning: soth.netfence.it: Host host-95-253-59-10.business.telecomitalia.it [95.253.59.10] claimed to be [192.168.147.11] Message-ID: Date: Mon, 29 May 2023 12:41:38 +0200 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: pnp4nagios replacement Content-Language: en-US To: Per olof Ljungmark , ports@freebsd.org References: <6fe9c668-87e0-a6ab-885f-e1810834e650@nethead.se> <9ef954f7-2817-b9c9-4c57-00dbc35d76ca@netfence.it> <42e42512-ac6f-964d-09a3-635bffe623ac@nethead.se> From: Andrea Venturoli In-Reply-To: <42e42512-ac6f-964d-09a3-635bffe623ac@nethead.se> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.86 X-Rspamd-Queue-Id: 4QVBsm0FHXz4SDb X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On 5/29/23 12:06, Per olof Ljungmark wrote: > Thank you Andrea, is nagiosgraph still alive? If yes, where? It's in port tree and it works. Alive? Not sure. Latest release is very old, so it's probably not well maintained. I switched from pnp to nagiosgraph, because it was a very little & fast task. Grafana, nagflux, icinga, etc... are probably more "alive", but switching is big work, so I though it was worth going the nagiosgraph way, even if only to postpone the problem. bye av.