Graylog2 / Graylog2/graylog2-server

Track and visualize cluster traffic by index set and index

Open
#16,083 0 comments 0 reactions 0 assignees View on GitHub
feature triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

## What?

Cluster traffic should be tracked on an `index set + index` basis, with the ability to focus on specific items in the UI, to help customers/users more easily identify the contributors to a given daily cluster traffic count.

## Why?

Currently there's a disconnect between the numbers shown when viewing daily cluster traffic and elsewhere. Even assuming a single index set and a daily rotation, the size of the index and the daily cluster traffic count don't match. This alone can be confusing, and mixing in non-daily index rotations (e.g. size-based) only add to the complexity.

While it's possible to use widgets to help identify the distribution for live data, that won't help for indexes that no longer exist. Additionally, customers might appreciate more insight into what contributes to the magic number that counts towards their license.

## Your Environment

* Graylog Version: 5.1.3

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.