Hey!
The static fields are not added by the input, even though the UI makes you
believe they are. In fact they are added during the filter chain execution,
which I from your description runs after the pipeline in your system.
The reason for adding the field later is that at the input level the
Hi!
It looks like you put the Java source file onto the classpath, which
doesn't work.
You need to compile it as part of your build (possibly as a graylog plugin,
or manually and then adding it to the classpath). The resulting file name
ends with .class, not .java.
The imports look good to
Hi Alexia!
This should work exactly as you configured it, the web interface will
connect to both servers in a round robin fashion.
The default heap sizes should not cause long GC pauses when faced with
moderate load, I doubt that this is the cause of these problems.
A couple of things to
Hi Jason!
Could you please turn the log level
of org.graylog2.security.ldap.LdapConnector to TRACE?
The easiest way to do so is via the System/Logging section in the API
browser (port 12900 of your graylog server).
That logs all kinds of details about the searches performed and the
entities
Hi!
No, that is currently not possible. Because messages are being processed in
parallel by multiple threads their order is not guaranteed at the moment.
The collector currently does not track the line numbers of the file it
reads, which could then be used to sort the messages again.
We do have
What Drew said, but starting with RC.4 the Group Object Class is Group
Search Filter and needs to be a valid filter:
(objectClass=group)
in the standard case.
On Wednesday, 9 September 2015 16:41:17 UTC+2, Drew Miranda wrote:
>
> Not sure if this helps but...
>
> Search Base DN should be the
Hi!
Old users should have been migrated to the new permission system
automatically, please check your graylog server log file. It should contain
lines like:
"INFO [UserPermissionMigrationPeriodical] Migrating permissions to roles
for user"
You can use roles without LDAP group mapping, yes.
On Tuesday, 8 September 2015 19:19:05 UTC+2, Mike Daoust wrote:
> Is it documented anywhere which versions of elasticsearch are suggested for
> graylog?
You should run the latest release version, but at least 1.6.x for the security
and reliability improvements.
Usually we aim to support the
Hi!
You need to build the Javascript bundle before running `activator dist` by
calling ./node_modules/.bin/gulp deploy-prod in javascript/.
Check the steps
in
https://github.com/Graylog2/graylog2-web-interface/blob/master/build_release.sh
for reference what we do to build a release.
cheers,
No, this should not be a timezone issue, as the extractors are re-checked
every second.
Do you have a lot of Grok patterns maybe?
On Saturday, 6 June 2015 00:43:46 UTC+2, Jesse Skrivseth wrote:
I don't have much new to report other than the observation that it takes
*exactly* 2 hours for
Jesse,
We've just tried to reproduce this issue on 1.1.0-RC.1 but it works as
expected.
Could you give that a try in a test environment, please?
Thanks,
Kay
On Saturday, 30 May 2015 13:42:52 UTC+2, Bernd Ahlers wrote:
Jesse,
thank you for the update. I created an issue in GitHub for this
Hi Ankit,
The blog post contains links to the log shipper at the very end of the post.
You can also access it via its Github
repository: https://github.com/Graylog2/collector
and https://github.com/Graylog2/collector/releases
cheers,
Kay
On Thursday, 21 May 2015 08:55:53 UTC+2, Ankit Mittal
12 matches
Mail list logo
