Application Management
MaxCustomFieldsLimitReached - Loggly
This article helps to address the customer custom fields limit notification from their derived fields in the Loggly account.
First published date
Last published date
Overview
- Derived Fields were missing or were not parsed or indexed properly.
- When navigating using Dynamic Field Explorer >> Loggly notifications field >> type then under the field actions, it is reporting MaxCustomFieldsLimitReached.
- When expanding your Events, under the notification field, you see this message like "4 out of 4 fields sent in this event were not indexed due to max allowed (50) unique fields being exceeded for this account."
Product section
Cause
Resolution
1. If you are affected, you should report it to Loggly Support. Please refer to the Support Policy on how to contact us.
2. Support will raise this to the Backend Engineering Team, subject to their approval in increasing the derived field limit of the account.
3. Engineering Team will assess the derived field usage count on the account.
4. If approved, they will increase the derived field usage limit on the account. The number of increasing the limit will be based on the assessment. For this process, there is no estimated time of completion.
5. Support will revert back to you that the derived field usage limit has been increased.
6. You will need to check on your account that fields on the Events are properly parsed and that "MaxCustomFieldsLimitReached" is already removed on the "notifications" field.
NOTES:
- Increasing the derived field usage limit does not incur any additional cost.
- There is no option of deleting derived fields in the Loggly UI.