-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add json_timestamp_layout option #8229
feat: Add json_timestamp_layout option #8229
Conversation
Is there any chance to get this PR merged into the upstream sources? It would greatly improve the chance for the integration of telegraf into a legacy environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the pull request, added two comments for you to review. Overall it looks good I think. I know its been a while since you've made this pr, are you still using this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, looks like there are some linter errors that will need to be fixed first before merging.
The linter errors are outside of this patch's scope, aren't they? |
The linter error The other linter error could be considered out of the scope |
Hi Sebastian,
I'm about to leave for a 10 days vacation trip right now, so please
expect some delay in my reaction.
And thank you for caring about my PRs.
--
Heiko
|
What's the next step? I'm asking, as, once it is merged, I'd care about my other PR (http unbatched output). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requesting a minor change for linter, then next steps would be someone else on the team needs to review this PR as well and then it can get merged. Thanks!
Hello, is there something I can do to get the changes approved? |
Apologies for the delay in getting to this PR. It looks like CI is failing because we've updated the required Go version from 1.16.6 to 1.17 since you made this PR. Please could you rebase off master and once CI passes we'd be happy to merge it. Thanks! |
Hi @popey , I rebased (and squashed) my changes onto the head of the current master. Please review again and tell me what changes are necessary to get it upstream. Thanks and Greetings from Dresden/Germany. |
Right now I changed the commit message to hopefully make the semantic pull request checker happy. And I seem to have succeeded :) @sspaink: thank you for the approval. Do I need to care that the actual merge will be done? |
Required for all PRs: