-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat] filebeat-7.15.0-apache-error-pipeline
doesn't recognize apache trace
log levels
#28650
Comments
Pinging @elastic/integrations (Team:Integrations) |
Hey @drenze-athene, thanks for reporting! I have opened #28717 and elastic/integrations#2064 to fix this in Beats and in the Apache integration. |
@jsoriano - NP. Ended up being a fairly easy fix in our instance. Didn't know what else in the pipeline might need to be updated, though. |
@drenze-athene what did you change in your instance? Current pipeline cannot parse this log line containing |
I have a CI/CD pipeline that uploads templates and ingest pipelines in our environment, and we don't override them once they've been uploaded (i.e., we don't deploy our beats with setup enabled). So after it was deployed, I edited the pipeline to include the following pattern definition: "APACHE_LOG_LEVEL" : "(emerg|alert|crit|error|warn|notice|info|debug|trace[1-8])" I included the complete functioning pipeline in my OP. |
Oh ok, so the change in the pipeline would be needed. Thanks! |
Absolutely. I looked at your change, didn't think of doing it that way. I just took the list of log levels specified in the Apache documentation and turned it into a regex. Yours was much easier. |
Apache error module ingest pipeline (
filebeat-7.15.0-apache-error-pipeline
) doesn't recognize apachetrace1 - trace8
log levels.The following entry in the Apache error log:
will generate the following error:
Resolution is to update the pipeline to include an
APACHE_LOG_LEVEL
definition. Working pipeline is as follows:Have not validated whether this is also required for the access pipeline or not.
For confirmed bugs, please report:
trace1 - trace8
log level.The text was updated successfully, but these errors were encountered: