You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Need separate events for input stopped and input deleted #7812
When an input is stopped either by the user or due to an error (deleted from the InputRegistry), an InputStopped event should be propagated by the EventBus.
When an input is deleted (deleted from the InputStateService), an InputDeleted event should be propagated by the EventBus
Current Behavior
Currently, an InputDeleted event is propagated by the EventBus in both cases (input stopped and input deleted). This makes it impossible for components to react to one event type but not the other.
Context
For a new Input with persistent state stored in MongoDB, I would like to delete the MongoDB record when the Input is deleted, but retain the MongoDB record when the input is stopped. This is currently impossible because both state transitions emit the same event type.
@Graylog2/architecture Has any more thought been given to this issue? It now seems to be at least part of the root cause of a customer issue described here: https://github.com/Graylog2/support/issues/148
Activity
Add workaround for input event problems in MongoInputStatusService
waab76 commentedon Jun 27, 2025
@Graylog2/architecture Has any more thought been given to this issue? It now seems to be at least part of the root cause of a customer issue described here: https://github.com/Graylog2/support/issues/148