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
When updating a grok pattern, the grok extractor should use the updated pattern.
Current Behavior
After updating a grok pattern, the grok extractor doesn't update and is still using the old pattern value. I had to restart the server to make it use the updated pattern.
Possible Solution
We send a GrokPatternsUpdatedEvent when a grok pattern gets updated. The grok extractor needs to listen for these and reload the patterns.
Steps to Reproduce (for bugs)
Create Grok pattern
Use Grok pattern in extractor
Update Grok pattern
Check logs that extractor is still using the old pattern
Your Environment
Graylog Version: 3.0.1
The text was updated successfully, but these errors were encountered:
Prior to this change, a edit on a grok pattern did not
reflect on the used pattern in GrokExtractors
This change uses the GrokPatternRegistry which is
contains all grok patterns and is connected to the
cluster event bus and reloads when a grok pattern is
edit.
One test needed to be moved since it was testing the
grok pattern service which is not used anymore in the
GrokExtractor directly. There for the test was moved
to the MongoDbGrokPatternServiceTest where it belongs.
Fixes#5833
Prior to this change, a edit on a grok pattern did not
reflect on the used pattern in GrokExtractors
This change uses the GrokPatternRegistry which is
contains all grok patterns and is connected to the
cluster event bus and reloads when a grok pattern is
edit.
One test needed to be moved since it was testing the
grok pattern service which is not used anymore in the
GrokExtractor directly. There for the test was moved
to the MongoDbGrokPatternServiceTest where it belongs.
Fixes#5833
* Use GrokPatternRegistry to reload saved grok patterns
Prior to this change, a edit on a grok pattern did not
reflect on the used pattern in GrokExtractors
This change uses the GrokPatternRegistry which is
contains all grok patterns and is connected to the
cluster event bus and reloads when a grok pattern is
edit.
One test needed to be moved since it was testing the
grok pattern service which is not used anymore in the
GrokExtractor directly. There for the test was moved
to the MongoDbGrokPatternServiceTest where it belongs.
Fixes#5833
Expected Behavior
When updating a grok pattern, the grok extractor should use the updated pattern.
Current Behavior
After updating a grok pattern, the grok extractor doesn't update and is still using the old pattern value. I had to restart the server to make it use the updated pattern.
Possible Solution
We send a
GrokPatternsUpdatedEvent
when a grok pattern gets updated. The grok extractor needs to listen for these and reload the patterns.Steps to Reproduce (for bugs)
Your Environment
The text was updated successfully, but these errors were encountered: