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

Data Routing: Insensitive toggles and error on Destinations page #20422

Open
danotorrey opened this issue Sep 11, 2024 · 2 comments
Open

Data Routing: Insensitive toggles and error on Destinations page #20422

danotorrey opened this issue Sep 11, 2024 · 2 comments

Comments

@danotorrey
Copy link
Contributor

danotorrey commented Sep 11, 2024

When on the Destinations Data Routing page, the toggle options for Index Set and Outputs seem to not work when clicked. There is no sign of progress or error when clicking them. Nothing seems to happen.

I also noticed the following error a while after the page loaded. It takes about 5 seconds to appear.
image

Loading index set with id: 6617f27053ebc348bd321744 failed with status: FetchError: There was an error fetching a resource: . Additional information: Cannot invoke "org.joda.time.Period.toStandardDuration()" because the return value of "org.graylog.plugins.datatiering.hotwarm.HotWarmDataTieringConfig.indexHotLifetimeMin()" is null

image

@danotorrey danotorrey changed the title Data Routing: Error when enabling outputs Data Routing: Insensitive toggles and error on Destinations page Sep 11, 2024
@tellistone
Copy link

by enabling, you mean "add output" ?

@danotorrey
Copy link
Contributor Author

danotorrey commented Sep 11, 2024

@tellistone Ahh, the Add Output option does actually work successfully. I think the issue is that the enable toggle controls on the rows are confusing. It seems to be just an indicator on if an Output/entry has been added or not. It seems to not respond to any user clicks. I think users would typically expect a toggle to do something when clicked. This is not a huge issue, but could lead to some user confusion. Maybe instead of using the toggle controls on this page, we could consider switching to Enabled/Disabled labels? I think that would be more clear for users that they don't need to click on them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants