---
title: Webapp - Chirp Log Review
created_date: 2025-09-15
updated_date: 2025-09-15
aliases:
tags:
---
# Webapp - Chirp Log Review

## Architecture

```mermaid
flowchart TD
  %% Clusters
  subgraph Client
    C1[Request upload URL]
    C2[Upload file via signed URL]
    C3[Request download URL]
    C4[Download file]
  end

  subgraph Flask
    F1[Generate signed upload URL]
    F2[Insert file metadata into Postgres]
    F3[Generate signed download URL]
  end

  subgraph S3
    S1[Object: flight123.chirp]
  end

  subgraph Postgres
    D1[(files table)]
    D2[(log_meta table)]
    D3[(log_timeseries table)]
  end

  %% Upload flow
  C1 -->|ask upload| F1
  F1 -->|return signed URL| C1
  C2 -->|PUT file| S3
  S3 -->|ack upload| C2
  F2 --> D1

  %% Download flow
  C3 -->|ask download| F3
  F3 -->|return signed URL| C3
  C4 -->|GET file| S3

  %% DB relations
  D1 --> D2
  D2 --> D3
```


## Feature Implementation Plan


## Future Feature Requests
- [ ] download plotjuggler binaries for different chirp versions
- [ ] download plotjuggler templates for different chirp versions
	- [ ] make a good one with background coloring, with parameter change indicators, etc
- [ ] download log analysis artefacts (pdf reports: generic, control, simplified, etc)
- [ ] Analysis and Flagging
	- [ ] check perf counters, every perf counter should have an okay range
	- [ ] check non-default parameters and highlight them
- [ ] make sure that timeseries parsing can be rerun (and it only reruns if there was a version change on how the timeseries data is processed or if there was an error)