Channels
announcements
ask-the-community
auth
conference-talks
contribute
databricks-integration
datahub-flyte
deployment
ecosystem-unionml
engineeringlabs
events
feature-discussions
flyte-bazel
flyte-build
flyte-console
flyte-deployment
flyte-documentation
flyte-github
flyte-on-gcp
flyte-ui-ux
flytekit
flytekit-java
flytelab
great-content
hacktoberfest-2022
helsing-flyte
in-flyte-conversations
integrations
introductions
jobs
konan-integration
linkedin-flyte
random
ray-integration
ray-on-flyte
release
scipy-2022-sprint
show-and-tell
sig-large-models
torch-elastic
workflow-building-ui-proj
writing-w-sfloris
Powered by
Title
a
Andrew Korzhuev
01/27/2023, 10:08 AM
Hello! Could you say why Flytekit logging format is different from Flyte logging?
https://github.com/flyteorg/flytestdlib/blob/master/logger/logger.go#L42-L50
https://github.com/flyteorg/flytekit/blob/master/flytekit/loggers.py#L66
This creates problem running the things on EKS for example, as you have to have multiple Fluent Bit parsers for each format to get correct logging level and timestamps later as you ingest the logs.
k
Ketan (kumare3)
01/28/2023, 4:46 AM
Cc
@Eduardo Apolinario (eapolinario)
@Andrew Korzhuev
this is a fair question- I think Eduardo is thinking of fixing it. Or you can contribute a or
e
Eduardo Apolinario (eapolinario)
01/28/2023, 7:26 AM
I opened
https://github.com/flyteorg/flyte/issues/3293
to track this. And as Ketan mentioned, this could be a good first contribution. 🙂
a
Andrew Korzhuev
01/30/2023, 11:00 AM
I left a comment on the issue, I think it should be standardized the other way round
#ask-the-community
Join Slack