Integration Package Management has significant flaws and needs to be enhanced

The Integration Package Management solution has some significant flaws and needs to be enhanced.  https://www.ibm.com/docs/en/instana-observability?topic=preview-sharing-reusing-instana-event-definitions.   I have found 2 significant limitations that make this extremely difficult to use or impossible.  Here are the 2 key problem areas:

If I create a Smart Alert against an application or Website and export it using stanctl-integration, the exported json contains the Application ID and/or website ID.   If I try to export these definitions from my Dev environment and import it into product, the import fails because the Application ID and Website ID are unique and different in the production environment.   If we used the Dashboard NAME and Website NAME, and the customer chose the same name in Dev and Production, then the import would be successful.   Or, if the names were different it would be easy for the customer to edit the json.   But, because we use the Application/Website ID, it is very difficult for the customer.  They must use the REST APIs to query and identify the appliction/website ID.  Then, update the JSON and then do the import.  Extremely painful.

Custom Dashboards are even worse.  When you export a dashboard, the dashboard has an owner.   When the dashboard is imported, the import fails because the user doesn't exist in the target Instana server.   In looking at the json, is isn't even the username that a customer could easily modify.  It is the user ID which will be unique from one environment to the next.   

Let's say the Tiger Team wants to publish a package for customers.   I can't publish a meaningful package because the customer environment will have different application IDs, website IDs, and different users from the environment where we did the export.

The Tiger Team is actively trying to export Events, Smart Alerts, and Custom Dashboards for a customer.