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

Content Pack installation does not detect existing Event Definition entities #19065

Open
williamtrelawny opened this issue Apr 15, 2024 · 1 comment

Comments

@williamtrelawny
Copy link
Contributor

Given a content pack containing:

  • a Correlation Event Definition ("ED-2") that relies on an underlying Event Definition ("ED-1")
  • the Event Definition ("ED-1") required by ED-2, and
  • the custom Stream tied to all Event Definitions

If the Stream and ED-1 already exist on the system and you install this new content pack, it will create a duplicate ED-1 but not a duplicate Stream.

This indicates there is some intelligent matching of Stream entities in Content Packs to pre-existing ones on the target system, but there is no such matching for Event Definitions.

Expected Behavior

If an Event Definition that a content pack provides already exists (by name not ID) on the target system, then content pack installation should skip the installation of its copy of the Event Definition.

Current Behavior

Content Pack installation creates a copy of the Event Definition (with a different object ID of course).

Possible Solution

Whatever intelligent matching is done for Streams in this fashion should be done as well for Event Definitions too.

Steps to Reproduce (for bugs)

  1. Install this Content Pack first
  2. Then install this one

Context

Affects my ability to install Correlation Event Definitions based on content previously built upon.

Your Environment

  • Graylog Version: 5.2.6
  • Java Version: bundled w/ Graylog
@williamtrelawny williamtrelawny changed the title Content Pack installation does not detect existing entities Content Pack installation does not detect existing Event Definition entities Apr 15, 2024
@waab76
Copy link
Contributor

waab76 commented Apr 24, 2024

Event Definitions have the same issue that Streams had where we only identify them by ID and do not enforce uniqueness on the names. This is a messy issue and we will need to consult with Architecture on how to approach this.

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