Skip to content

Need separate events for input stopped and input deleted #7812

Closed

Description

@waab76

Expected Behavior

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.

Activity

  1. added this to the 4.0.0 milestone on Apr 28, 2020
  2. removed this from the 4.0.0 milestone on Jan 27, 2022
  3. waab76 commented on Jun 27, 2025

    @waab76
    ContributorAuthor

    @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

  4. self-assigned this
    on Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions