Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it possible to configure multiple RELP target servers #143

Open
plkokanov opened this issue Jul 22, 2024 · 2 comments
Open

Make it possible to configure multiple RELP target servers #143

plkokanov opened this issue Jul 22, 2024 · 2 comments
Labels
area/ipcei IPCEI (Important Project of Common European Interest) kind/enhancement Enhancement, improvement, extension lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/5 Priority (lower number equals higher priority)

Comments

@plkokanov
Copy link
Collaborator

How to categorize this issue?

/kind enhancement

What would you like to be added:
Make it possible to configure multiple RELP target servers. Additionally, make it possible to choose separate log inputs and logging rules per target. Potentially there could be multiple log inputs per 1 target.

Why is this needed:
This would allow users to forward logs to multiple servers. For instance, audit logs could be forwarded to two logging servers - one where they are kept for short period of time for quick analysis and one where they are kept for longer (cold storage). In addition, this would allow users to use the shoot-rsyslog-relp extension for other logs as well.

@gardener-prow gardener-prow bot added the kind/enhancement Enhancement, improvement, extension label Jul 22, 2024
@JordanJordanov JordanJordanov added area/ipcei IPCEI (Important Project of Common European Interest) priority/5 Priority (lower number equals higher priority) labels Aug 7, 2024
@gardener-ci-robot
Copy link

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Mark this issue as rotten with /lifecycle rotten
  • Close this issue with /close

/lifecycle stale

@gardener-prow gardener-prow bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 5, 2024
@gardener-ci-robot
Copy link

The Gardener project currently lacks enough active contributors to adequately respond to all issues.
This bot triages issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close

/lifecycle rotten

@gardener-prow gardener-prow bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ipcei IPCEI (Important Project of Common European Interest) kind/enhancement Enhancement, improvement, extension lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/5 Priority (lower number equals higher priority)
Projects
None yet
Development

No branches or pull requests

3 participants