- Activities
- Alarms
- Audit
- Buckets
- Clearance
- Commands
- COP-1
- Database
- Events
- File Transfer
- IAM
- Indexes
- Instances
- Links
- MDB Override
- MDB
- Packets
- Parameter Archive
- Parameter Lists
- Parameter Values
- Processing
- Queues
- Replication
- RocksDB
- Server
- Services
- Sessions
- Stream Archive
- Table
- Time Correlation
- Time
- Timeline
Yamcs Release Notes
Yamcs Server Manual
Source Code Documentation
Rebuild RangeΒΆ
Rebuild range
The back filler has to be enabled for this purpose. The back filling process does not remove data but just overwrites it. That means that if the parameter replay returns less parameters than originally stored in the archive, the old parameters will still be found in the archive.
It also means that if a replay returns the parameter of a different type than originally stored, the old ones will still be stored. This is because the parameter archive treats parameter with the same name but different type as different parameters. Each of them is given an id and the id is stored in the archive.
URI Template
POST /api/archive/{instance}/parameterArchive:rebuild
{instance}
Yamcs instance name.
Request Body
// Note that the archive is built in segments of approximatively 70 minutes,
// therefore the real start will be before the specified start and the real
// stop will be after the specified stop.
interface RebuildRangeRequest {
// Start rebuilding from here. Specify a date string in ISO 8601 format.
start: string; // RFC 3339 timestamp
// Rebuild until here. Specify a date string in ISO 8601 format.
stop: string; // RFC 3339 timestamp
}