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.

Sign up for GitHub

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

Jump to bottom

Setup Log Stash+Kibana for Accumlo and Fluo #254

Closed
keith-turner opened this issue Jun 5, 2019 · 2 comments
Closed

Setup Log Stash+Kibana for Accumlo and Fluo #254

keith-turner opened this issue Jun 5, 2019 · 2 comments

Comments

@keith-turner
Copy link
Contributor

keith-turner commented Jun 5, 2019 •
edited
Loading

Muchos currently sets up grafana and influx db for metrics. It would be nice if it also setup something for logging. One possibility is log stash and kibana. Log stash and kibana support indexing specialized log messages. For Accumulo it would be nice to create a schema for indexing the following log messages.

  • Loaded a tablet
  • Log recovery on a tablet
  • Compaction on a tablet
  • Closing a tablet.
  • GC deleted a file

The schema could pull out the key extent, table ID, and files from these messages. Having a schema for the above would allow quick searches for important events. This activity may result in a positive feedback loop that helps improve Accumulo's log messages.
@keith-turner keith-turner mentioned this issue Aug 8, 2019
Open
@keith-turner keith-turner mentioned this issue Sep 23, 2019
Closed
@plainolneesh
Copy link
Contributor

I am working on this ticket.

plainolneesh added a commit to plainolneesh/fluo-muchos that referenced this issue Mar 10, 2020
@plainolneesh
wip - apache#254
10130e7
@ctubbsii ctubbsii mentioned this issue Jul 16, 2020
Merged
@arvindshmicrosoft
Copy link
Member

Implemented as part of #338.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@keith-turner @plainolneesh @arvindshmicrosoft