Provide string prefix/identifier in connector sync logs to distinguish log messages written by source/destination vs written by Airbyte #5889
Assignees
Labels
Milestone
Comments
|
@cjwooo could be having the container name as an identifier helps? (source, destination, scheduler, server) |
|
@davinchia / @Phlair is it possible to estimate what is needed to change to implement this feature? |
This was referenced Oct 21, 2021
benmoriceau
added a commit
that referenced
this issue
Oct 22, 2021
This is preparing the tagging of the application that generate a log which is requested in #5889 It is adding helper to add a color to the log and safely manipulate the MDC. It is also modifying the log4j pattern. The use of those helper will will be implemented in another PR.
benmoriceau
added a commit
that referenced
this issue
Oct 28, 2021
This is adding the application name in the logs produced by the docker containers. This is related to #5889.
schlattk
pushed a commit
to schlattk/airbyte
that referenced
this issue
Jan 4, 2022
This is preparing the tagging of the application that generate a log which is requested in airbytehq#5889 It is adding helper to add a color to the log and safely manipulate the MDC. It is also modifying the log4j pattern. The use of those helper will will be implemented in another PR.
schlattk
pushed a commit
to schlattk/airbyte
that referenced
this issue
Jan 4, 2022
) This is adding the application name in the logs produced by the docker containers. This is related to airbytehq#5889.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tell us about the problem you're trying to solve
Our use case for Airbyte involves surfacing sync logs to our users. We only want to show the logs written by the actual source and destination, e.g.
and not the ones written by Airbyte, e.g.
Describe the solution you’d like
A procedure for distinguish logs written by source or destination vs written by Airbyte in the response given by calling
api/v1/jobs/get.Describe the alternative you’ve considered or used
A clear and concise description of any alternative solutions or features you've considered or are using today.
Additional context
Add any other context or screenshots about the feature request here.
Are you willing to submit a PR?
Remove this with your answer :-)
The text was updated successfully, but these errors were encountered: