Are there any plans to add a systemd input to get access to some logs in 2023 that are roughly equivalent to the ones collected from /var/log/messages, /var/log/dmesg, and /var/log/secure via the fluent-bit host-log.conf in AL2? I'm not sure exactly which services would fall into that bucket, but it seems like something would be useful, perhaps things like systemd-networkd, systemd-logind, cloud-init?
I guess this may be a bit cart-before-horse since aws-for-fluent-bit doesn't seem to be quite ready to consume systemd logs on AL2023, but I'd very much like to keep the level of out-of-the-box observability we're accustomed to from EKS on AL2 when we move to AL2023.
Are there any plans to add a systemd input to get access to some logs in 2023 that are roughly equivalent to the ones collected from
/var/log/messages,/var/log/dmesg, and/var/log/securevia the fluent-bithost-log.confin AL2? I'm not sure exactly which services would fall into that bucket, but it seems like something would be useful, perhaps things likesystemd-networkd,systemd-logind,cloud-init?I guess this may be a bit cart-before-horse since
aws-for-fluent-bitdoesn't seem to be quite ready to consume systemd logs on AL2023, but I'd very much like to keep the level of out-of-the-box observability we're accustomed to from EKS on AL2 when we move to AL2023.