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

Better process to update content packs #3517

Open
HyderNBK117 opened this issue Feb 17, 2017 · 2 comments
Open

Better process to update content packs #3517

HyderNBK117 opened this issue Feb 17, 2017 · 2 comments

Comments

@HyderNBK117
Copy link

This issue comes from this inquiry - https://community.graylog.org/t/how-to-update-content-packs-in-the-webapp/112.

Its situation around the Content packs functionality - menu from the top -> System -> Content Packs

Current situation is that there are multiple Graylog instances deployment servicing a development environment (Local, DEV, UAT, LIVE/Production). A Content pack was created and now is replicated throughout each environment.

Expected Behavior

Create an update to a content pack which does duplicate, triplicate etc items when a content pack is applied.

Current Behavior

Every time you click 'Apply Content' it adds the entire contents again, meaning it will duplicate, triplicate etc etc

Possible Solution

Have another option to update the current content pack, currently when you select Apply Content it doesn't check if there is an already existing item.

Steps to Reproduce (for bugs)

  1. Create Content pack
  2. Upload to new server/instance
  3. Click Apply Content - Content will be added
  4. Click Apply Content - Same Content will be added again

Context

I'm trying to synchronize different environments which represent different stages through a development cycle.

Your Environment

  • Graylog Version: 2.2
  • Elasticsearch Version:2.4.4
  • MongoDB Version:3.2
  • Operating System:RedHat Enterprise 6.6
  • Browser version:Chrome
@h0tw1r3
Copy link

h0tw1r3 commented Jul 13, 2017

Expected behavior should be: Duplicates are updated.

We have the same setup in our environment. We use puppet to maintain content-packs, which is great for initial provision, but any updates need to be applied manually 👎 . Obviously this doesn't happen too often, but occasionally it is necessary to update a grok pattern or extractor.

@lennartkoopmann lennartkoopmann changed the title How to update Content Packs in the WebApp Better process to update content packs Oct 9, 2017
@luciano-coder
Copy link

Hi,

I'm facing the same issue at the moment and wondered if anyone has a decent workaround for this? For instance, is it possible to remove and install via the API?

Many Thanks

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

6 participants