POST Endpoint for Instana Event REST API

Currently there is no simple way to create Alerts or Alert Channels using the Instana API. Only the PUT method exists which can be used to Create or Update these resources. However, these endpoints require unique IDs to perform these actions, which we seem to need to have to define ourselves for new Alerts or Channels. This is quite unusual, as it looks like the only way (or at least one of the only ways) to create one of these resources is to generate a random string ID, then retrieve all the existing Alerts or Channels and make sure the generated ID does not match any of them - to ensure that existing resources are not overwritten by accident - before using said ID to create a new resource.

This seems like over-engineering a solution that should really be encapsulated by the API in the form of a POST endpoint that creates a resources and returns the created object with its unique, server-assigned ID, especially since this sort of functionality is usually defined as best practice for RESTful Web API design. The PUT standards state:

Whether to support creation via PUT depends on whether the client can meaningfully and reliably assign a URI to a resource before it exists. If not, then use POST to create resources and have the server assign the URI, then use PUT or PATCH to update.

Since the IDs seem completely random, and because they can be created programmatically via the API or through the UI, I don't think the client can meaningfully and reliable assign a URI to a resource. The server must already handle this ID creation functionality for Alerts and Channels that are created through the UI anyway, so it should be reasonably straightforward to extend this to a simple POST endpoint for the API.