Graylog2 / Graylog2/graylog2-server

Indexing & Processing Failures Displayed Statuses Inconsistent with System Configuration Settings

Open
#15,219 1 comment 0 reactions 0 assignees View on GitHub
bug to-verify triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

By default in 5.x, all Failure Processing options under System > Configurations are disabled,yet under System > Overview, Indexing Failures appears enabled whereas Processing Failures does not. If you enable Processing Failures in System > Configuration, the corresponding status in System > Overview shows enabled as expected. So it appears there is no way to disable Indexing Failures.

Also, when Processing Failures is disabled, the status display box is gray, but the check mark remains instead of turning into a warning symbol like when the *Search cluster status display turns red.

## Steps to Reproduce (for bugs)

1. Default state- when System > Configurations > Failure Processing all options disabled, System > Overview > Indexing & Processing Failures shows a gray box with a white check mark and status _"Disabled"_:
![image](https://user-images.githubusercontent.com/98823025/231863909-d030bb4c-b76b-46b8-b8e8-542373a2cc1d.png)
2. When enabling Log Processing Failures in System > Configuration, System > Overview shows all green:
![image](https://user-images.githubusercontent.com/98823025/231864155-bb380fd9-4b02-4e61-8adc-eda2f67e936c.png)
3. When enabling Log Indexing Failures in System > Configurations, System > Overview shows no change in status for either option from default.
4. For reference, when *Search backed becomes unavailable the status box turns red and the circle check mark turns to a triangle exclamation point, as expected when any of these status messages show disabled or a warning:
![image](https://user-images.githubusercontent.com/98823025/231864773-7fc582e8-5fb9-4292-9a60-30aa3b0abf2f.png)

## Context
Unsure if Log Processing Failures are indeed disabled or if Log Indexing Failures are indeed enabled in the default configuration. Or if this all this is just a presentation level bug. I have not been able to generate either type of message failure to test.

## Your Environment

* Graylog Version: 5.0.3 (see [comment](https://github.com/Graylog2/graylog2-server/issues/15219#issuecomment-1508456564) for more info)
* Java Version: bundled w/ Graylog
* Opensearch Version: 2.5.0
* MongoDB Version: 6.0.4
* Operating System: Debian 11.6
* Browser version: Chrome 112

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.