Each application within Timber has it's own dynamic schema. Here's a short list that describes it's behaviour:
- Your schema is maintained on the fly, as data is received.
- Your schema is typed, subsequent values for the same field will be coerced into this type if it does not match.
- Your schema is only limited as described in the service limits doc.
- Your schema is automatically maintained, if a field has not been received within your plan's retention window, it will be removed.