Skip to content
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

Allow configuring envoy's application log format for better integration with observability tooling #7214

Closed
bartsmykla opened this issue Jul 10, 2023 · 5 comments
Labels
kind/feature New feature triage/rotten closed due to lack of information for too long, rejected feature...

Comments

@bartsmykla
Copy link
Contributor

Description

It would be beneficial to allow configuring envoy application logging format (probably json would be enough), which would allow better integration with observability tooling (like Datadog)


ref. https://www.envoyproxy.io/docs/envoy/latest/configuration/observability/application_logging#printing-logs-in-json-format

application_log_config:
  log_format:
    json_format:
      Timestamp: "%Y-%m-%dT%T.%F"
      ThreadId: "%t"
      SourceLine: "%s:%#"
      Level: "%l"
      Message: "%j"
      FixedValue: "SomeFixedValue"
@bartsmykla bartsmykla added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Jul 10, 2023
@michaelbeaumont michaelbeaumont added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Jul 10, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Oct 9, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 9, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Oct 9, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jan 8, 2024
Copy link
Contributor

github-actions bot commented Jan 8, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz added triage/rotten closed due to lack of information for too long, rejected feature... and removed triage/stale Inactive for some time. It will be triaged again triage/accepted The issue was reviewed and is complete enough to start working on it labels Jan 8, 2024
@jakubdyszkiewicz jakubdyszkiewicz closed this as not planned Won't fix, can't repro, duplicate, stale Jan 8, 2024
@jakubdyszkiewicz
Copy link
Contributor

Triage: we found a way to configure this in Datadog itself (different processor)

@slonka
Copy link
Contributor

slonka commented Jan 8, 2024

it's in https://app.datadoghq.com/logs/pipelines -> name -> kuma-cp > steps 1 & 2

Copy link
Contributor

github-actions bot commented Jan 8, 2024

Automatically closing the issue due to having one of the "closed state label".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/rotten closed due to lack of information for too long, rejected feature...
Projects
None yet
Development

No branches or pull requests

4 participants