Dear friends,
I have been using graylog 4.0 for a long time but now I have an error that I need to fix.
To log messages from windows systems I use a specific input channel and a stream that
forward all of these messages in a particular index (windows).
Unfortunately, as you can see from the message below, the type value is not enough to record everything and it needs to be increased
windows_0 239e0f53-dc23-11ec-9172-001a4a16018f ElasticsearchException[Elasticsearch exception [type=illegal_argument_exception, reason=Limit of total fields [1000] has been exceeded]]
I see some guides and threads without any improvements:
I need to change the default value, 1000, for âtypeâ value using a custom template
for this index.
Can anybody help me to solve this case ?
Thanks a lot
Bye
Willy
You can raise the limit but there are potential drawbacks to that - here is a good Graylog article on it
Also - Here is a previous post where we talked through finding and reducing the number of fields.
Finally of note - I believe the 1000 fields limit is per index set - if you can split out what you are doing into another index set (or more) that may address the issue.
now Iâd like to know how I can change the default value for new windows_* index
that will be created when graylog make a rotation. I need to set type to 2000.
I still think you need to look at why you are ending up with over 1000 fields - here is an example post of syslog Input with Fortigate where the input needed to be changed to RAW since the Syslog input was creating new fields for each message because it was parsing improperly. Alternatively you can split incoming to different indexes so that you reduce the number of fields in the index.
Dear all,
Iâm using some index , for example one for cisco one for fortigate and so on. The problem is that only inside window.index and I think that the limit that I need to be set is about 1400. The problem is occurr after rotation because when the new index was spawn it has got a default value, 1000. I set a new value only for windows_* index inside elastisearch.yml config file ? Are there any other possibilities ?
Thanks again
Windows systems logs
Index prefix: windows
Shards: 8
Replicas: 0
Field type refresh interval:5 seconds
Index rotation strategy: Index Time
Rotation period: P1M (1 month, a month)
Index retention strategy: Delete
Max number of indices: 12
now Iâve got two index and your command works fine , but it can be applied only to the windows_0
and windows_1 index, it doesnât change the default value for the index windows_2,3,4,⊠which will be generated when the rotation mechanism deems it appropriate.