| 16 Nov 2023 |
 jwitrick_91242 | * hey all. not sure what the overall process is but i created a PR in logging-operator: https://github.com/kube-logging/logging-operator/pull/1582 | 17:49:53 |
| jwitrick_91242 | * hey all. not sure what the overall process is but i created a PR in logging-operator: https://github.com/kube-logging/logging-operator/pull/1582 | 17:49:57 |
| 17 Nov 2023 |
 pepov | Adding Opensearch field endpoint to supp... | 06:51:07 |
 xinity77 | hey folks, as we have fluentbit a daemonset, how it would beneficial to offer some HA for the central fluentD instance ? | 09:07:50 |
| pepov | hey folks, as we have fluentbit a | 09:18:38 |
| 21 Nov 2023 |
| xinity77 | is there any workaround to avoid modifying sysctl configuration on GKE for example when using the logging operator ? | 10:05:27 |
| pepov | is there any workaround to avoid | 13:18:45 |
|  ivoriesablaze joined the room. | 19:07:00 |
| 22 Nov 2023 |
| xinity77 | how to efficently debug a flow ? i'd like to make sure a configured flow is correctly grabing logs , any hints on this ? | 11:14:43 |
| pepov | how to efficently debug a flow ? i'd | 12:35:46 |
| 24 Nov 2023 |
|  nakof_75462 joined the room. | 14:24:47 |
| 25 Nov 2023 |
|  arta.eth joined the room. | 03:25:25 |
|  quantumcat40 joined the room. | 13:47:17 |
| quantumcat40 | We currently have a standalone fluentbit deployment in Kubernetes, it is picking up application metrics, with parse rules and sending them directly to influxdb. We want to use logging operator but don’t see an output supported for influxdb. Is this possible and if so would anyone have an example? | 13:49:38 |
 WrenIX | FluentD generates prometheus metrics based on the flow-filter (and the default fluentbit metrics exists) - you could configure your influxdb to scrape them | 22:36:12 |
| WrenIX | https://docs.influxdata.com/influxdb/v2/write-data/no-code/scrape-data/manage-scrapers/ | 22:39:39 |
| WrenIX | Or use telegraf therefore | 22:39:55 |
| WrenIX | https://github.com/influxdata/telegraf/blob/master/plugins/inputs/prometheus/README.md | 22:40:33 |
| WrenIX | * FluentD generates prometheus metrics based on the [flow-filter](https://kube-logging.dev/docs/configuration/plugins/filters/prometheus/) (and the default fluentbit metrics exists) - you could configure your influxdb to scrape them | 22:41:40 |
| WrenIX | PS: but maybe you want to take a look into the prometheus-operator.dev as well - it has many benefits inside of kubernetes (e.g. the helmchart of the logging-operator is able to deploy servicemonitor todo that jobs on an kubernetes-operatorpattern way) | 22:49:14 |
| 27 Nov 2023 |
| ivoriesablaze | Hello, I have a Rancher instance with Logging Operator set up going an Elasticsearch server. When I tail /fluentd/log/out in the fluentd pod, I get error="400 - Rejected by Elasticsearch" location=nil
. In the clusteroutput, I have
spec:
elasticsearch:
buffer:
timekey: 1m
timekey_use_utc: true
timekey_wait: 30s
host: boc22entapplog.fau.edu
include_timestamp: true
index_name: egrades
log_es_400_reason: true
port: 9200
Despite the fact I have log_es_400_reason: true, I still get the same message without a reason. I'll add that it appears at least some of the logs do come through to Elasticsearch. Does anyone one know what the next step I should take is? | 14:01:05 |
| ivoriesablaze | * Hello, I have a Rancher instance with Logging Operator set up going an Elasticsearch server. When I tail /fluentd/log/out in the fluentd pod, I get error="400 - Rejected by Elasticsearch" location=nil
. In the clusteroutput, I have
spec:
elasticsearch:
buffer:
timekey: 1m
timekey_use_utc: true
timekey_wait: 30s
host: ---------------
include_timestamp: true
index_name: ----------
log_es_400_reason: true
port: 9200
Despite the fact I have log_es_400_reason: true, I still get the same message without a reason. I'll add that it appears at least some of the logs do come through to Elasticsearch. Does anyone one know what the next step I should take is? | 14:04:17 |
| pepov | Hello, I have a Rancher instance with | 15:25:14 |
|  gingimli | 21:01:29 |
| gingimli | Hey, is there a way to remove or override the command that gets applied to the fluent bit Pods?
``` containers:
- command:
- /fluent-bit/bin/fluent-bit
- -c
- /fluent-bit/etc-operator/fluent-bit.conf | 21:03:52 |
| gingimli | * Hey, is there a way to remove or override the command that gets applied to the fluent bit Pods?
containers:
- command:
- /fluent-bit/bin/fluent-bit
- -c
- /fluent-bit/etc-operator/fluent-bit.conf
| 21:03:57 |
| 28 Nov 2023 |
| pepov | Hey, is there a way to remove or | 09:30:55 |
| 29 Nov 2023 |
|  gamba47 joined the room. | 13:59:58 |
| gamba47 | Hi guys how are you? I'm starting with logging-operator. I have a EKS cluster sending logs to NewRelic and S3 bucket (in the same account). I want to try now send logs from specific deployments to Cloudwatch.
I created output and flow resources but there is nothing in CW. I had checked iam permissions using aws-cli.
My doubt is how can I see logs in this case? I'm using stern to check all logs from the cattle-logging-system namespace and there are a lot of information but I can figure out what are the steps to try to see the error.
See you! | 14:32:43 |
| gamba47 | I read the docs but I can´t find yet any tip to get in the wright path | 14:40:52 |
