 | Logging Operator | 183 Members |
| 5 Servers |
| Logging Operator | 183 Members |
| 5 Servers |
| Sender | Message | Time |
|---|---|---|
| 15 Dec 2023 | ||
 haxodon_35576 joined the room. | 20:33:30 | |
| 17 Dec 2023 | ||
 WrenIX | Logging-operator-logging is legacy, it is part of logging-operator (with values.yaml under logging - logging.enabled is the importents :) ) | 23:54:28 |
| WrenIX | * Logging-operator-logging is legacy, it is part of logging-operator in oci repo (with values.yaml under logging - logging.enabled is the importents :) ) | 23:58:38 |
| 18 Dec 2023 | ||
 zipzad | Hey there 🙂 We have some extremely verbose pods in some namespaces without flows/outputs, we don't want them to go in the logging pipeline as it adds Gigs of useless load. Any idea how to tackle that? | 16:06:55 |
| 19 Dec 2023 | ||
 steveizzle | Hey i have got a problem and your bug tracker says i should first contact you via chat to rule out config errors: Multiple times i observed the behavior, that when i do simple changes to the logging CR fluentd is broken afterwards with the same error and stops working: ..... 2023-12-19 09:06:17 +0000 [warn]: #0 [main_forward] unexpected error before accepting TLS connection by OpenSSL addr="10.194.147.129" host="10.194.147.129" port=37090 error_class=OpenSSL::SSL::SSLError error="SSL_accept returned=1 errno=0 peeraddr=10.194.147.129:37090 state=error: certificate verify failed (self-signed certificate in certificate chain)" 2023-12-19 09:06:17 +0000 [warn]: #0 [main_forward] unexpected error before accepting TLS connection by OpenSSL addr="10.194.147.89" host="10.194.147.89" port=41520 error_class=OpenSSL::SSL::SSLError error="SSL_accept returned=1 errno=0 peeraddr=10.194.147.89:41520 state=error: certificate verify failed (self-signed certificate in certificate chain)" 2023-12-19 09:06:18 +0000 [warn]: #0 [main_forward] unexpected error before accepting TLS connection by OpenSSL addr="10.194.147.197" host="10.194.147.197" port=36424 error_class=OpenSSL::SSL::SSLError error="SSL_accept returned=1 errno=0 peeraddr=10.194.147.197:36424 state=error: certificate verify failed (self-signed certificate in certificate chain) ..... This time i only changed bufferVolumeResources! When i do a simple rollout restart of the fluentd statefulset it simply works again... Any ideas? | 09:31:23 |
 overorion | TLS error (self-signed certificate) | 09:48:52 |
 tru64guru_78072 joined the room. | 14:01:44 | |
 sdesbure joined the room. | 15:05:05 | |
 pafchuimort joined the room. | 18:14:18 | |
| 21 Dec 2023 | ||
 quantumcat40 | Hi, we are using the Logging Operator that is bundled with Rancher. We have an issue where the Logging Operator sends to ELK for a few days but then it suddenly stops working. Restarting the fluend-root container seems to get things running again. We also get this error constantly: | 15:27:39 |
| 22 Dec 2023 | ||
 dipak_49549 joined the room. | 07:22:37 | |
 dipak140 joined the room. | 07:26:42 | |
| dipak140 | Hi, for K8s version 1.25 and above, PodSecurityPolicy in version "policy/v1beta1" has been removed, hence i am getting the following error, this has also meant that my current logs have stopped flowing as well. | 07:28:08 |
| dipak140 | dipaksisodiya@Dipaks-MacBook-Air logging % helm upgrade --install --wait --create-namespace --namespace logging logging-operator oci://ghcr.io/kube-logging/helm-charts/logging-operator --version=4.5.0 Pulled: ghcr.io/kube-logging/helm-charts/logging-operator:4.5.0 Digest: sha256:4339f18a2d4ea2e2dff8ced57137340b5eef3f0fd22f793280f406c5e22cc087 Error: UPGRADE FAILED: unable to build kubernetes objects from current release manifest: resource mapping not found for name: "psp.logging-operator" namespace: "logging" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first | 07:28:51 |
 playmtl | Hey, i solved this error with a documentation from rancher: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards#cleaning-up-releases-after-a-kubernetes-v125-upgrade | 11:42:44 |
| playmtl | * Hey dipak140 , i solved this error with a documentation from rancher: https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/pod-security-standards#cleaning-up-releases-after-a-kubernetes-v125-upgrade | 11:42:57 |
| dipak140 | Hey playmtl It worked! Thanks for the quick response! | 12:08:26 |
| 26 Dec 2023 | ||
 blagi_65247 joined the room. | 22:31:38 | |
| blagi_65247 | Please don't hold it against me if this question seems a bit naive, but I've been looking for an answer for quite some time and just can't seem to find it anywhere. I need to install an EFK stack, but I want Fluentd to directly send logs to Elasticsearch, instead of creating copies like, for example, in /var/lib/docker. I'm looking for something more along the lines of /var/lib/containerd/{pod_id}/logs or /var/log/containers/{pod_id}/log. Otherwise, the logs are taking up too much space on my disk. Also, I'm using a storageClass and not an emptydir, so I need the logs on Elasticsearch and stored on an external disk, or rather, storageClass. Is this something kube-logging can handle? Thank you very much! | 22:49:36 |
| 27 Dec 2023 | ||
 pepov | Please don't hold it against me if this | 15:04:00 |
| pepov | 🎄 Hey! I hope everyone had / is having a wonderful Christmas! 📚 Docs are now updated and available for 4.5: https://kube-logging.dev/docs/whats-new/ 🙏 Huge thanks for everyone involved! | 16:23:34 |
| pepov | * Hey! I hope everyone had / is having a wonderful Christmas! 🎄 📚 Docs are now updated and available for 4.5: https://kube-logging.dev/docs/whats-new/ 🙏 Huge thanks for everyone involved! | 16:23:59 |
| 3 Jan 2024 | ||
 sunc363587351 joined the room. | 05:18:03 | |
 whok8s_08944 joined the room. | 10:19:36 | |
 whok8s joined the room. | 10:27:32 | |
 eudyptes_mosleyi joined the room. | 15:11:43 | |
| 4 Jan 2024 | ||
 celestial_dolphin_45229 joined the room. | 21:23:32 | |
| 5 Jan 2024 | ||
 sg2566 | the message content is not json so you need to parse your content. You need 2 parsers (these are just dummy values) 1. /^(?<field_1>[^ ]) (?<timestamp>[^ ]) (?<field_2>[^ ]) (?<field_3>[^ ]) APP-METRIC (?<body>).... 2. json parser for the <body> field | 21:19:55 |
| sg2566 changed their display name from Sg to sg2566. | 21:19:55 | |
| 6 Jan 2024 | ||
| quantumcat40 | Thank you sg2566 . I think I get the idea sort of. What type of parser would the first one be? Do you know if there is a more complete example somewhere? Would it be the fluentd documentation? Sorry really new to this stuff | 00:08:27 |