From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4g0SHx28d4z33Dm for ; Tue, 21 Apr 2026 16:20:13 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4g0SHt0RJYz2xQW for ; Tue, 21 Apr 2026 16:20:10 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (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) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4g0SHs1Z75z2sm for ; Tue, 21 Apr 2026 16:20:09 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1776788409; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=cEdPREmrLWBIJD/gmo/iEc/o7t7oUnzrYeaQVd7ygAM=; b=2JV4FQm61iXZTpqHTPBl3rvPsk5QP34VSoFxfLJLOpcSeB+fgqDfmZ74B2n1QDUXTBb/60 f3zI4HvOPoxh+7DQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1776788409; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=cEdPREmrLWBIJD/gmo/iEc/o7t7oUnzrYeaQVd7ygAM=; b=fbyQXV5YHb6faewj9BEJYVcA5ZFSo4Rfq4ATaf2gyQvErrk4zjxb9UHD1IL3SlQAkxroGD 4ynSVGxWP7y64TktmFRsOd0L0l/leiMWonTO4WN8BtCLd9XvmDva0a5uOns1DWRhhmhzOU pyZXR/s9PpN7vgKfLQQRSTs5q/qO3fawO5YF5QUMFyiN7x4VapycgBgXS5xY8iZmJDHo/C rVN3HR5mKqN3/Zw+sAuOBew+WFeB2AT7f7qaRPfHIM5JdRu8WQxmT8PdRvMaqlAFpaIrqO M/ZBygrRxW1k3+KmbCkEtmPOr09R72RLubnVQVLz7Vs+rlDsg5lJFUTB+wFc/g== Message-ID: Date: Tue, 21 Apr 2026 18:20:05 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Language: en-GB To: "IPFire: Development-List" From: Adolf Belka Subject: Question about potential consequence of patch to rotate Suricata logs daily. Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Michael, I saw that patch https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=30ccb9ed80ee3ad70403794da4c937fd183b9bd8 had been created. It seems to me that this change will mean that there will only ever be 52 days worth of logs for Suricata. The global value for rotate is 52 which is intended to give a tear's worth of data for the various graphs. With the Suricata logs being rotated daily and with the same global rotate value ( there is no modified rotate value for the Suricata section) then there will only ever be 52 days worth of Suricata Logs. This will mean that the Suricata throughput graph will only show about 7 weeks worth of data when the Year option is selected. Was this the intent? If not then there probably needs to be a rotate entry in the Suricata section with rotate 393 to give a year's worth of data but then that will put back the same amount of logs for people who have very small disk drives. If yes then maybe the Year option on the Suricata graph should be removed or changed to 7 weeks as the 52 days would then be around 7.5 weeks of data available. It could also be that I am not familiar enough with the rotate package and therefore my concerns are not valid. So I am open to getting clarification. Best regards, Adolf.