Registered files
0
Available for analysis
Pipeline
Processing
ActiveCurrent workspace: Processing
Page usage manualManual
Processing guide
Use processing pages to run parser jobs and convert raw log evidence into engineering outputs.
What it provides
- Queued, running, completed, and failed job state.
- Parser profile, decoder, and format capability visibility.
- Analysis output that feeds signals, rules, findings, reports, and AI context.
How to use it
- 1. Run analysis for a queued log file.
- 2. Choose a project and registered log file.
- 3. Run or retry the analysis job when action is available.
- 4. Review decoder results and generated statistics before moving to signals.
Outcome: Raw logs become structured signal statistics and decoded evidence for engineering review.
Processing jobs
0
Created from uploads
Completed jobs
0
Signal statistics ready
Engineer6 assigned projects
Assigned project analysis queue
Engineers run analysis for assigned project logs, review parser output, and continue to signals, rules, findings, reports, and AI context.
Jobs
Run queued analysis jobs, retry failed parsers, and inspect processing state.
analysis execution
Analysis runs
Inspect generated signal statistics and analysis output for each log file.
engineering metrics
Decoder results
Review decoded network signals, DBC context, and parser output coverage.
CAN/DBC context
Parser and Signal Readiness
Engineering state of the ingestion-to-statistics pipeline for the selected workspace.
Completion rate
0%
0 completed of 0
Parser capability
0%
0 active format definitions
Signal outputs
0
statistics on selected log
Analysis readiness
25%
Weighted from parser support, completed jobs, failed jobs, and selected-log statistics.
Workflow state
Registered
0
log files
Queued
0
waiting
Completed
0
processed
Failed
0
needs review
Parser profile usage
No datawaiting for evidence
Processing Jobs
Parser execution history for registered project logs.
| Log File | Job Type | Status | Analysis profile | Updated |
|---|
Loading...