You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When adding a stage to config.snippets.pipelineStages in helm values, it looks like it's not templated correctly. Some values seems like they are too long and are spilling over to the next line, invalidating the config? I'm trying to capture multiline logs. I know the regex is correct, but the multiline logs are not getting grouped into one when viewing in Grafana.
To Reproduce
Steps to reproduce the behavior:
Started Loki (2.9.2)
Started Promtail (2.9.2) to tail '...'
Query: {} term
Expected behavior
I expect that the pipeline_staqges config will remain when it's evaluated into a config for promtail. In my case, it's affecting the multiline stage, but it seems that this can affect anything that is using a long string value.
Environment:
Infrastructure: EKS
Deployment tool: helm
Screenshots, Promtail config, or terminal output
This is the helm config for promtail
pipelineStages:
- cri: {}
- match:
selector: '{app="my-app-name"}'
stages:
- multiline:
# Identify timestamps as first line of a multiline block. Enclose the string in single quotes.
firstline: '^\[\d{4}-\d{2}-\d{2}T\d{1,2}:\d{1,2}:\d{1,2}\.\d{3}\] \[\w+\] \w+ -'
max_wait_time: 3s
- regex:
# Flag (?s:.*) needs to be set for regex stage to capture full traceback log in the extracted map.
expression: '^(?P<time>\[\d{4}-\d{2}-\d{2}T\d{1,2}:\d{1,2}:\d{1,2}\.\d{3}\]) \[\w+\] \w+ - (?P<message>(?s:.*))$'
Here is an example log [2023-11-15T22:29:30.537] [INFO] default - Successfully connected to backend.
This is the relevant snippet from promtail's config that is generated
Note how the firstline and expression values flow into the next line.
Something is happening when the helm chart is evaluates the values and stuffs the promtail.yml config into a secret... which is loaded into promtail to use as it's config.
The text was updated successfully, but these errors were encountered:
Describe the bug
When adding a stage to
config.snippets.pipelineStages
in helm values, it looks like it's not templated correctly. Some values seems like they are too long and are spilling over to the next line, invalidating the config? I'm trying to capture multiline logs. I know the regex is correct, but the multiline logs are not getting grouped into one when viewing in Grafana.To Reproduce
Steps to reproduce the behavior:
{} term
Expected behavior
I expect that the
pipeline_staqges
config will remain when it's evaluated into a config for promtail. In my case, it's affecting themultiline
stage, but it seems that this can affect anything that is using a long string value.Environment:
Screenshots, Promtail config, or terminal output
This is the helm config for promtail
Here is an example log
[2023-11-15T22:29:30.537] [INFO] default - Successfully connected to backend.
This is the relevant snippet from promtail's config that is generated
Note how the
firstline
andexpression
values flow into the next line.Something is happening when the helm chart is evaluates the values and stuffs the
promtail.yml
config into a secret... which is loaded into promtail to use as it's config.The text was updated successfully, but these errors were encountered: