Datamodel acceleration date range forced to last month

[joshiro]

Hi, i need help with some datamodel acceleration issues in CIM.

The problem is that i accelerated a datamodel with 1y summary range, but after rebuilding it, i cant get results older than last month, neither in pivot or tstats from datamodel. The command datamodel works fine with older events.

Tried to tweak the advanced configuration in the datamodel acceleration settings, but nothing changed.

The query using tstats:

| tstats prestats=true local=false summariesonly=true allow_old_summaries=true count from datamodel=Network_Traffic.All_Traffic by _time,All_Traffic.transport span=10m
| timechart minspan=10m count by All_Traffic.transport

Am i missing some configuration that forces the acceleration date range to the last month range?
Appreciate any insight about this issue.

EDIT: this are the configuration settings

allow_old_summaries = true

allow_skew = 0

backfill_time = -1y

cron_schedule = 1-56/5 * * * *

earliest_time = -1y

hunk.compression_codec = -

hunk.dfs_block_size = 0

hunk.file_format = -

manual_rebuilds = false

max_concurrent = 9

max_time = 3600

poll_buckets_until_maxtime = true

schedule_priority = highest

workload_pool = -

Update1: We noticed that several acceleration mainenance searches were skipped, so we optimized the datamodel acceleration specifying the used index, made the scheduled maintenance searches run at diferent times so they dont overlap, and reduced the time range of the datamodels.

[joshiro · Accepted solution]

Check Update1 in the opening post for a solution that worked for us.

[scelikok]

Hi @joshiro,

Please check backfill range value. It may be 1 month long. That is why older data may not be accelerated.

[joshiro]

Changed backfill range to 1y, but it didnt solve the problem.
Thanks for the suggestion.