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
auto_multi_line_extra_patterns is not supported #570
Comments
Is it difficult to add an option in the chart for each possible option in the agent. it the values.yaml file datadog:
env:
- name: DD_LOGS_CONFIG_AUTO_MULTI_LINE_DETECTION
value: "true" please let me know if it solve the log agent configuration issue. |
I have used this parameter and value just as you mentioned, this helped to enable the auto detection of multiline logs with the For my case I need P.S. Using |
@sullerandras did you get it to work by setting |
Hi @sullerandras |
Hi @clamoriniere , # Under datadog:
env:
- name: "DD_LOGS_CONFIG_AUTO_MULTI_LINE_DETECTION"
value: "true"
... omitted lines ...
logs_config:
auto_multi_line_detection: true Unfortunately I have java multiline logs like starts with I've tried to add the EXTRA_PATTERNS as ENV variables as you mentioned (see bellow code) but from inside the container the I got MULTI_LINE_DETECTION value changed to false: # Under datadog:
env:
- name: "DD_LOGS_CONFIG_AUTO_MULTI_LINE_EXTRA_PATTERNS"
value: ^23-03.* ### also tried with quoted "^23-03.*"
- name: "DD_LOGS_CONFIG_AUTO_MULTI_LINE_DETECTION"
value: "true" ### also tried without quotes
... omitted lines ...
logs_config:
auto_multi_line_detection: true |
I was able add the extra patterns as env var thanks to the single quote: `` agents:
containers:
agent:
env: # to only set the env var to the container responsible of logs.
- name: DD_LOGS_CONFIG_AUTO_MULTI_LINE_DETECTION
value: "true"
- name: DD_LOGS_CONFIG_AUTO_MULTI_LINE_EXTRA_PATTERNS
value: '^23-03.*' the agent status output:
|
Thanks @clamoriniere for fast reply, # Under datadog:
env:
- name: "DD_LOGS_CONFIG_AUTO_MULTI_LINE_DETECTION"
value: "true"
... omitted lines ...
logs_config:
auto_multi_line_detection: true |
Thank you @clamoriniere and every one else here, # Under datadog:
env:
- name: "DD_LOGS_CONFIG_AUTO_MULTI_LINE_DETECTION"
value: "true"
... omitted lines ...
## logs_config: # Removed
## auto_multi_line_detection: true # Removed |
hi again @vrej-abramian that is why adding For now what you can do is: datadog:
logs:
enabled: true
#...
autoMultiLineDetection: true
agents:
containers:
agent:
env:
- name: DD_LOGS_CONFIG_AUTO_MULTI_LINE_EXTRA_PATTERNS
value: '^23-03.*' And it should work. please let me know if it finally works for you. |
Hey @clamoriniere, This did not work ( from within container the multi_line_detection is not enabled
|
Thanks for all the replies. I set the env variable but i'm not sure what should i set it to. Our application is running in a kubernetes cluster, and we log using JSON. Mostly works fine, however, long json logs are cut at 8192 bytes, and the rest is going on a new line. This must be a line length limit somewhere, i'm not sure where. So basically all log lines start with |
With latest 2.32.3: Setting only one of |
@keatsfonam good finding, I did not used the |
Hi, I am having problem with how to provide the value field for DD_LOGS_CONFIG_AUTO_MULTI_LINE_EXTRA_PATTERNS in case there are multiple patteerns. thanks. |
Also, what should be the patterns for log lines like these?
|
@iahmad-khan, assuming that all your logs start with
Kind reminder: Please consider using a test environment and test configurations for specific issues/cases. |
Hi,
But still the exception logs are not coming in single line for java springboot application. agent: 7.37.1-jmx Thanks |
Hi @clamoriniere and @vrej-abramian , Helm chart v3.3.3 Here is my scenario with step by step:
Then upgrade datadog-agent by helm command. This is my agent config:
Then upgrade datadog-agent again. This is my agent config:
|
hi @dyleph I was not able to reproduce the issue that you describe. Could you check when it happens that the value is properly set in and also in the daemonset resource that with only thanks 🙇 |
Hi @dyleph, @clamoriniere, If you want to get rid of the |
Hi @clamoriniere and @vrej-abramian, ATM, the logs are aggregated as well on datadog agent after I set both configs: About configure JSON logging from the application, I did try by writing consoleLog and fileLog with JSON format. |
Try removing the |
The
logs_config.auto_multi_line_extra_patterns
option is described in this doc but it looks like it's not supported by the helm chart.Would it be possible to add support for this?
The text was updated successfully, but these errors were encountered: