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

Add access logs and error logs to the Filebeat nginx dashboard #5240

Merged
merged 1 commit into from
Sep 27, 2017

Conversation

monicasarbu
Copy link
Contributor

Reorganize the visualizations in the Nginx dashboard and add access and error logs.

Here is a screenshot of the dashboard.
filebeat nginx access and error logs

cc-ed @simianhacker

@simianhacker
Copy link
Member

simianhacker commented Sep 25, 2017

For the "response codes over time" chart I would group by filters and then create the following 4 filters:

  • Set label to 200s and filter to nginx.access.status_code:[200 to 299] and color to green
  • Set label to 300s and filter to nginx.access.status_code:[300 to 399] and color to yellow
  • Set label to 400s and filter to nginx.access.status_code:[400 to 499] and color to red
  • Set label to 500s and filter to nginx.access.status_code:[500 to 599] and color to magenta

image

@simianhacker
Copy link
Member

For "Errors over time" I would change the bar color to solid red.

@monicasarbu
Copy link
Contributor Author

monicasarbu commented Sep 26, 2017

I split the dashboard into two dashboards: one that is an overview and the other one that has the Nginx logs.

filebeat nginx access and error logs
filebeat nginx overview

@monicasarbu monicasarbu force-pushed the nginx_dashboard_filebeat branch from be131ad to ca99bf8 Compare September 27, 2017 11:04
Copy link
Contributor

@tsg tsg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WFG

@kvch kvch merged commit e0d7c16 into elastic:master Sep 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants