public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [RFC common 0/1] Optional parameters `since` and `until` for firewall log filtering
Date: Thu,  5 Jan 2023 10:18:02 +0100	[thread overview]
Message-ID: <20230105091804.156599-1-c.ebner@proxmox.com> (raw)

This patch series introduces 2 optional api parametes `since` and `until` to firewall log
endpoints, in order to make them filterable.

In contrast to the current `dump_logfile`, the specialized `dump_fw_logfile` takes into
consideration and scans also rotated logfiles, if `since` or `until` are given.

Without optional parameters, `dump_logfile` is used.

Christian Ebner (1):
  tools: Add specialized `dump_fw_logfile` for `since` and `until`
    filtering of firewall logs

 src/PVE/Tools.pm | 80 ++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 80 insertions(+)

Christian Ebner (1):
  api: Add optional parameters `since` and `until` for timestamp filter

 src/PVE/API2/Firewall/Host.pm | 15 ++++++++++++++-
 src/PVE/API2/Firewall/VM.pm   | 18 +++++++++++++++---
 2 files changed, 29 insertions(+), 4 deletions(-)

-- 
2.30.2





             reply	other threads:[~2023-01-05  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  9:18 Christian Ebner [this message]
2023-01-05  9:18 ` [pve-devel] [RFC firewall] api: Add optional parameters `since` and `until` for timestamp filter Christian Ebner
2023-01-05 13:51   ` Fiona Ebner
2023-01-05 13:59     ` Thomas Lamprecht
2023-01-05 14:27       ` Christian Ebner
2023-01-05  9:18 ` [pve-devel] [RFC common 1/1] tools: Add specialized `dump_fw_logfile` for `since` and `until` filtering of firewall logs Christian Ebner
2023-01-05 13:25   ` Wolfgang Bumiller
2023-01-05 14:25     ` Christian Ebner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230105091804.156599-1-c.ebner@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal