Risotto Bias unusualevent · they/them
unusualevent closed issue ornithopter/ornithopterhosting.com#2 2025-01-11 04:53:13 +00:00
Pricing
unusualevent commented on issue ornithopter/ornithopterhosting.com#2 2025-01-11 04:53:12 +00:00
Pricing

updated.

unusualevent opened issue ornithopter/ornithopterhosting.com#2 2025-01-03 08:27:30 +00:00
Pricing
unusualevent opened issue go/decal#2 2025-01-02 10:24:49 +00:00
verbs/actions/objects
unusualevent commented on issue misc/oskoreia#8 2024-12-31 23:04:50 +00:00
comparison - loki (AGPL)

if prefix includes the processing node (/cache_policy/retention_policy/collector_id/host_id/epoch_ms/chunk_ms.sqlite.gz.age) then two simultaneous collectors could upload. when new epoch is made,…

unusualevent commented on issue misc/oskoreia#8 2024-12-31 22:55:36 +00:00
comparison - loki (AGPL)

log collectors by default don't have the private keys they're encrypting to, so they can't by default read until a cache request condition comes in. that could be separated out by requiring a hot…

unusualevent commented on issue misc/oskoreia#8 2024-12-31 21:07:49 +00:00
comparison - loki (AGPL)

90 day upload API key anyway?, automatically rotate age keys (auto-rotate syslog keys too? - syslog addresses are just upload ones, but could have them expire after 2 years?), maybe 90 min, 2 year…

unusualevent commented on issue misc/oskoreia#8 2024-12-31 20:46:15 +00:00
comparison - loki (AGPL)

some log processors will only be uploaders, so could be writing to a public key they don't have a read on.

unusualevent commented on issue misc/oskoreia#8 2024-12-31 20:45:26 +00:00
comparison - loki (AGPL)

configurable: age key rotations and partitioning key phases: per-log-processor age key (in multiples of 7, so that's 13 age keys in play in 90 days) log processor does not keep around older age…

unusualevent commented on issue misc/oskoreia#8 2024-12-31 20:25:23 +00:00
comparison - loki (AGPL)

cache policy is a bounded-and

  • one of {128mb, 2,000 events, 15 minutes}
  • and one of {512mb, 10,000 events, 1 hour}

^ allow them to tune that.

  • web dash host (manages API keys,…
unusualevent commented on issue misc/oskoreia#8 2024-12-31 19:38:31 +00:00
comparison - loki (AGPL)

forgot the max amount of data that can be stored in a cipher before you need a new key, but ideally the recipient encryption should be readable on multiple boxes (e.g. ingest-A's key, ingest-B's…

unusualevent commented on issue misc/oskoreia#8 2024-12-31 19:00:03 +00:00
comparison - loki (AGPL)

index format sqlite tables (for logs vs for user preferences/searches):

need to relate: ingest api key, ingest time, event time, host, log source, tags -> which chunk it's in -> raw log

folde…

unusualevent commented on issue misc/oskoreia#8 2024-12-31 18:10:13 +00:00
comparison - loki (AGPL)

sqlite index: on ingestion box, tag log batches, compress in chunks (e.g. 15 minute increments, 2,000 EPS, or 128mb, whichever is larger) - old project idea was parquet, drill, minio (no zookeeper…

unusualevent commented on issue misc/oskoreia#8 2024-12-31 17:44:19 +00:00
comparison - loki (AGPL)

it's not glamorous and scalable, it doesn't trust the S3 storage (age encrypted, minisign signed), sqlite indexing, $10/TB stored, search is throttled, ingest is throttled (.5 TB/month) but can be…

unusualevent opened issue misc/oskoreia#8 2024-12-31 16:59:15 +00:00
comparison - loki (AGPL)
unusualevent opened issue misc/hephaestus#2 2024-12-31 15:39:08 +00:00
witness / binary transparency / sigstore
unusualevent opened issue misc/trailhead#2 2024-12-31 15:37:17 +00:00
implement sigsum interface
unusualevent created repository go/crux 2024-12-30 00:32:34 +00:00
unusualevent created repository go/potential 2024-12-30 00:29:40 +00:00