| 20 Jul 2023 |
 mranno | okay, thank you 🙂 | 09:34:31 |
 grg_2145 | it looks like that the sync is only every week, but boke 2 weeks ago, but it broke with access denied we might need some time | 09:37:51 |
| mranno | (the sync should be triggered automatically every time any internal testdb branches are pushed) | 09:38:58 |
| mranno | * (the sync should be triggered automatically every time any internal testdb branches are pushed. at least that was how it originally worked 🙂 ) | 09:39:50 |
| grg_2145 | yes you're right(it did not tried because it was broken) Folti Fixed it for us, it sjould be in sync now | 09:51:33 |
| mranno | it's green, thank you 🙂 | 11:00:15 |
|  cerregulus joined the room. | 12:44:45 |
| 21 Jul 2023 |
|  y-eight joined the room. | 07:44:51 |
|  y_eight joined the room. | 07:50:48 |
|  liquidanalysator joined the room. | 08:34:16 |
| 24 Jul 2023 |
|  Tobias Müller joined the room. | 10:00:19 |
| 25 Jul 2023 |
 czp | Hi | 14:45:13 |
| czp | A question about "parallelize() support for pipelines" | 14:45:21 |
 bazsi77 | https://github.com/buytenh/ivykis/pull/25 | 14:48:18 |
| czp | So, even if I update ivykis in EPEL 9 and Fedora, I need to recompile syslog-ng as well. | 14:48:20 |
| bazsi77 | This is one reason we started to offer containers, these things get messy easily. I am not sure if that feature is crucial for those who use the distro packages, it addresses a niche case, where a single chatty client sends a lot of messages to syslog-ng | 14:49:02 |
| czp | I'll definitely add this patch to Fedora Rawhide, there are no barriers there. EPEL 9 is a tougher question: I might skip it, as it's a many weeks project with multiple barriers. But I can make my own Fedora / RHEL repos have a modified ivykis. | 14:56:02 |
| bazsi77 | we are also talking to Lennert to help the maintenance of ivykis somehow so that the patch can be incorporated. | 14:56:51 |
| bazsi77 | but the last release of ivykis is relatively old. | 14:57:02 |
| czp | OK, just checked: FreeBSD also uses the bundled ivykis version. | 15:03:11 |
| czp | So, I only need extra work on Fedora / RHEL. | 15:03:24 |
| czp | "only": that's our most used platform where I maintain both the official and unofficial packages... 😄 | 15:04:31 |
|  dankgus joined the room. | 15:23:58 |
| 26 Jul 2023 |
|  el_satan joined the room. | 06:09:06 |
| el_satan | Can somebody help me with the syslog-ng config? I'm moving from Rancher-Logging (which uses the "old" 3.17 logging operator chart) to the new 4.2.3 Chart but having a hard time getting syslog-ng to work.
First off, the logging.enable did nothing for me, I had to create the logging resource by myself. For the start I have a HTTP ClusterOutput that (should) put logs to Loki and two Flows that have it as the globalOutputRefs. But the syslog-ng pod can't start and inspecting the generated syslog-ng.conf I can see, that the generated logs point to a non existing destination rather than the loki destination which is also there. Am I missing something? This is one of my Flows and the cluster output:
---
apiVersion: logging.banzaicloud.io/v1beta1
kind: SyslogNGFlow
metadata:
name: nginx
namespace: ingress-nginx
spec:
globalOutputRefs:
- loki
match:
and:
- regexp:
pattern: ingress-nginx
type: string
value: json.kubernetes.labels.app.kubernetes.io/instance
---
apiVersion: logging.banzaicloud.io/v1beta1
kind: SyslogNGClusterOutput
metadata:
name: loki
namespace: logging
spec:
http:
url: http://loki-gateway.loki
| 06:28:04 |
| bazsi77 | pepov can you offer some help here? | 06:39:08 |
| el_satan | Redacted or Malformed Event | 06:41:03 |
 pepov | Can somebody help me with the syslog ng | 06:43:20 |
| czp | 
Download sng43norm_vs_parallelize.png | 10:38:37 |
| czp | I used my sngbench script to compare configurations with and without the new parallelize() feature of syslog-ng 4.3.0 | 10:38:38 |
