Hi,
I followed https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html and used as many defaults from this page as possible.
The doc states (uppercase mine):
Fluent Bit logstream name is fluent-bit-PODNAME-POD-NAMESPACE
My Cloudwatch logs logtream are created with names like this:
MYPREFIXkube.var.log.containers.PODNAME_POD-NAMESPACE_POD-NAMESPACE-c84369ae77ac89dc13db1d49dfdf9333e5d6e192d897468a34e532969d4052d3.log
It feels like the pattern in the doc isn't what's really happening -- or shouldn't I expect Fluent Bit logstream to equate log stream name ?
|
The logs are in CloudWatch in the same {aws} Region as the cluster. The log group name is `[.replaceable]``my-cluster``-fluent-bit-logs` and the Fluent Bit logstream name is `fluent-bit-[.replaceable]``podname``-[.replaceable]``pod-namespace```. |
Hi,
I followed https://docs.aws.amazon.com/eks/latest/userguide/fargate-logging.html and used as many defaults from this page as possible.
The doc states (uppercase mine):
My Cloudwatch logs logtream are created with names like this:
MYPREFIXkube.var.log.containers.PODNAME_POD-NAMESPACE_POD-NAMESPACE-c84369ae77ac89dc13db1d49dfdf9333e5d6e192d897468a34e532969d4052d3.log
It feels like the pattern in the doc isn't what's really happening -- or shouldn't I expect Fluent Bit logstream to equate log stream name ?
amazon-eks-user-guide/latest/ug/nodes/fargate-logging.adoc
Line 342 in d4530ee