Let API created alerts link to Assets (including Custom Assets), and show alert history on the Asset page

We're building an integration that posts alerts into Gorelo via POST /v1/alerts/ for devices that can't run the Gorelo agent. In our case, UniFi devices, tracked as Custom Assets. Two related gaps make this less useful than it should be:

1. No way to link an alert to a specific asset at creation time. POST /v1/alerts/ only accepts a ClientId, not an AssetId (or equivalent). Alerts show up correctly attributed to the client, but the device name is just free text. It doesn't link to the actual asset record, even when an asset with a matching name already exists.

2. Custom assets only show ticket history, not alert history. The asset detail page has a Ticket tab, but nothing equivalent for alerts, so there's no way to see "what's fired for this device" from the asset's own page, even for alerts that are correctly attributed to the right client.

To fix this properly, we think it needs two pieces working together, not just one:

• Expose Custom Assets via the API (currently GET /v1/assets/agents only returns agent-based assets). A way to list/search them by name would let integrations resolve the right asset automatically instead of requiring manual ID lookups per device.

• Accept an AssetId on POST /v1/alerts/ so external alerts can be explicitly linked to the correct asset (agent-based or custom) when created.

With both in place, it'd also be worth showing alert stats/history on the Custom Asset page itself, mirroring what already exists for tickets.

Happy to provide more detail on our specific use case if helpful.