Data layout - usage help

[bfloriang]

Hi there,

I've been playing around with the prefiller after finding a reference on (prometheus/prometheus#535) but I'm struggling to get the tool working for me.

I notice that the directory and file layout that results from running prefiller looks different than an empty Prometheus data store just created by bringing Prometheus up (I tried version 1.7.1 and 1.8.2).

After running prefiller:

[XXX@XXX data]$ tree
data
├── archived_fingerprint_to_metric
│   ├── 000001.log
│   ├── CURRENT
│   ├── LOCK
│   ├── LOG
│   └── MANIFEST-000000
├── archived_fingerprint_to_timerange
│   ├── 000001.log
│   ├── CURRENT
│   ├── LOCK
│   ├── LOG
│   └── MANIFEST-000000
├── heads.db
├── labelname_to_labelvalues
│   ├── 000001.log
│   ├── CURRENT
│   ├── LOCK
│   ├── LOG
│   └── MANIFEST-000000
├── labelpair_to_fingerprints
│   ├── 000001.log
│   ├── CURRENT
│   ├── LOCK
│   ├── LOG
│   └── MANIFEST-000000
├── mappings.db
└── VERSION

Fresh Prometheus installation

/prometheus/data # ls *

99:
6bf7c4f0744d30.db  81c763c5f4d943.db  8d67781712ca9b.db  a0d965e6535daf.db  b394c82595132c.db  eb84fea15ae0a8.db  f4b4c142823c09.db

9a:
54201d6ae73552.db  6806be24a5ce00.db

de:
0e7d051f319666.db  f43a6192e1be9c.db

df:
02d74982a0fffa.db  10cbca521ed1cd.db  17a83d5b652ca7.db  5a507fbaf0dfc3.db  a23eb2338abee9.db  aaa3bb99297f27.db  aaf0e130a90c18.db  e4f026f3b83be1.db  f8b3d8510ca802.db

It would be much appreciated if you could show where to map the resulting data store on an existing Prometheus installation.