BlackMaple.FMSInsight.Cli.linux-x64
17.1.2
dotnet add package BlackMaple.FMSInsight.Cli.linux-x64 --version 17.1.2
NuGet\Install-Package BlackMaple.FMSInsight.Cli.linux-x64 -Version 17.1.2
<PackageReference Include="BlackMaple.FMSInsight.Cli.linux-x64" Version="17.1.2" />
<PackageVersion Include="BlackMaple.FMSInsight.Cli.linux-x64" Version="17.1.2" />
<PackageReference Include="BlackMaple.FMSInsight.Cli.linux-x64" />
paket add BlackMaple.FMSInsight.Cli.linux-x64 --version 17.1.2
#r "nuget: BlackMaple.FMSInsight.Cli.linux-x64, 17.1.2"
#:package BlackMaple.FMSInsight.Cli.linux-x64@17.1.2
#addin nuget:?package=BlackMaple.FMSInsight.Cli.linux-x64&version=17.1.2
#tool nuget:?package=BlackMaple.FMSInsight.Cli.linux-x64&version=17.1.2
Insight CLI
insight-cli reads Insight history into a private SQLite database and queries it locally. It can be
used interactively or from scripts and agents. All server requests are read operations, including
the job-history POST; SQL queries use a read-only connection.
Install the tool with the .NET 11 SDK and run insight-cli --help.
dotnet tool install --global BlackMaple.FMSInsight.Cli
Windows x64 and Linux x64 get self-contained executables. Other supported platforms use the portable
build with the .NET 11 runtime. To redistribute the standalone Windows CLI, copy insight-cli.exe,
README.md and LICENSE from tools/any/win-x64/ in BlackMaple.FMSInsight.Cli.win-x64.
When running from the repository root during development, substitute
dotnet run --project client/cli -- for insight-cli in the examples below.
insight-cli sync --server http://cell-controller:5000 --database study.sqlite \
--from 2026-10-01T00:00:00Z --to 2026-10-08T00:00:00Z
insight-cli sync --server http://cell-controller:5000 --database study.sqlite
insight-cli query --database study.sqlite --sql "SELECT * FROM metadata"
insight-cli query --database study.sqlite --sql-file cycles.sql --format csv > cycles.csv
insight-cli material --server http://cell-controller:5000 --database study.sqlite --id 123
insight-cli status --server http://cell-controller:5000 > status.json
insight-cli program --server http://cell-controller:5000 --name 123 --revision 2 > program.nc
Use a private directory and a new database path for the first sync. It requires both time bounds;
later runs resume that window, and a later --to extends it. Times require Z or an explicit UTC
offset. Source, lower bound or cache-schema changes require a new path. Keep existing evidence and
stop the writer before copying its database. Check the source after a checkpoint conflict; rebuild
at a new path if necessary.
Set INSIGHT_TOKEN to an externally obtained bearer token when required. Credentials are not stored
in the cache. SQL defaults to stdin and JSON output; --format csv includes a header. Results go to
stdout and diagnostics to stderr. Check the exit code before using output, which may be partial on
error or cancellation. Ctrl+C cancels a running command.
Inspect metadata, coverage, material_coverage and unresolved_job_references before analyzing
results. complete means the last sync finished; job_context_complete separately indicates
whether referenced plans were available. Neither proves complete material lifecycles or inspection
outcomes. material --serial SERIAL retrieves every matching material ID; matches can be ambiguous.
Targeted reads have separate coverage and do not advance global event progress. Status and program
reads do not update the historical cache.
Inspect the schema with SQL such as SELECT name,sql FROM sqlite_schema WHERE type='table' or
PRAGMA table_info(events). The main tables are events, event_material, material, jobs,
job_decrements, casting_actions, schedules, sim_station_use and sim_station_parts.
Durations are seconds; timestamps are UTC.
- Filter event times for a bounded analysis: targeted history and supporting corrections can lie outside the sync window. Selected schedules are retrieved in full and can also extend beyond it.
jobs.plan_jsoncontains historical planning. Comments, holds, bookings and archive/delivery state remain only in response provenance. Original response JSON is not a historical snapshot of live state. Decrements are reconciled separately; jobcyclesis the original planned quantity.- Elapsed time is recorded wall time; active time is the planning target. Count shared cycles and simulated station intervals once before joining their material or job participants.
- Material metadata on old events reflects the backend when retrieved. Casting actions preserve their own assignment context. Older servers may lack assignment/decrement events; unrecorded actions cannot be recovered. A long catch-up can require a large response from the server's unpaged recent-events endpoint.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 17.1.2 | 0 | 11/19/2026 |