-
Content packs should be able to define a minimum version of `graylog-server` they need to function properly. Graylog should then check against this value during import.
See also #3250.
-
Graylog plugins should be able to hook into the content packs functionality. For example, our processing pipelines functionality is currently a plugin but pipelines, rules, etc should be able to be in…
-
Would it be possible to track the URL path as a separate field?
-
### Problem description
When importing content pack, that runs into trouble, the import process tries to roll back.
It looks like it ignores or doesn't rollback the Grok patterns,
Everything else (In…
-
Entity codecs should return the version constraints (Graylog version, plugin version) when creating the entity representation for content packs.
Refs #4220
-
When creating a contents pack, you have to select the items to include. In my case I just wanted to export all of my custom grok patterns to import onto a different Graylog instance. At the top of all…
-
When installing a specific version of a content pack, Graylog needs to do the following things:
* Ask user for parameters defined in content pack
* Check validity of version constraints
* Check v…
-
I have a graylog cluster setup, and receiving the following error in the logs;
2018-09-26T14:08:30.076+01:00 INFO [InputStateListener] Input [Syslog UDP/5a982448687cf8128c10ce6e] is now STOPPING
…
r4yfx updated
5 years ago
-
Content packs that are listed in the `content_packs_auto_load` config option are only applied automatically if the content pack has not been installed yet.
If the user decides to enable the auto load…
bernd updated
6 years ago
-
Remove the old content pack (configuration bundle) functionality from the web interface and the Graylog server, so that only the new content packs functionality remains.