Lukas Rist

Add a button to create a new sensor

2

Button opens modal with form for sensor name. Create a new backend endpoint `POST /sensors` to create new sensors. Sensor names are unique per user, not globally. Confirming form creates...

Authenticate sensors by sensor UUID

4

If the event comes from a sensor with valid UUID, accept the event

New endpoints to return config and rules by sensor uuid

2

Add a new endpoint GET /configs Add a new endpoint GET /rules Populate the config with the Ochi details.

The backend will have access to binaries for each architecture. UUID of the sensor needs to be baked into binary. Use the following snippet to replace a placeholder sensor UUID...

Move parameters into config file

2

We pass service configuration as parameters. We should use a config file instead. Create config file if it doesn't exist. Default config shoold have configuration for local testing. Use github.com/hashicorp/hcl/v2 ...

Apply all enable, saved queries to incoming events

2

I agree this ended up to be much more complex from a UX point of view. I wonder if a better approach would be to show on the main page...

Fixed layout should be dynamic

6

The [App.svelte](https://github.com/glaslos/ochi/blob/d2d71c0030943d0def48bd43c595b82ad95f5060/src/App.svelte#L216-L259) has a lot of hard-coded layout glory. This makes is rather difficult to add new layout elements without breaking the current layout. Even adding new pages would be...

Improved filter input

1

Currently, we have a fixed-size input field limiting usability when providing multiple filter rules. Look at [Greynoise](https://viz.greynoise.io/ip/8.8.8.8) input field for inspiration. - On focus, expand the input field's width -...

Add syntactic content assistance to the filter field

3

This is a feature of chevrotain, documentation is [here](https://chevrotain.io/docs/guide/syntactic_content_assist.html) I don't think we need to be concerned regarding the performance but have a look at the related section in the...