Define, export and import named ServiceControl connections

[odelljl]

We support several ServiceControl instances in our environment.

• In down-level (DEV/QA/TEST) scenarios, it is a simple case of managing separate instances for each environment.
• We also have the issue in production, as we support our Azure Service Bus along with multiple SQL endpoints. These SQL endpoints are integration endpoints for external applications using the Native integration

To facilitate our use cases, it would be beneficial if:

• When a connection is defined in the User Interface, the user can optionally define an alternate short Service Name.
• If a Service Name is not defined, the Service Name defaults to what it is today.

• When presented in the Endpoint Explorer, we see - or have the options to see - this Service Name in the list
• ServiceControl allows the Export and Import of the connection list based on the Service Name as the identifier of each Endpoint connection

This is somewhat related to Issue #998. I would suggest sorting on the Service Name.

[OranguTech]

Please, at the very least the ability to give human readable names to endpoints would get us like 80% of the benefits, perfect for a first-pass feature change.

We currently have to maintain a manually updated internal wiki entry of what endpoints are on what ports. We are currently at 16 entries.

[HEskandari]

@OranguTech I think what you are asking is different than this issue. This issue is about naming the connection to ServiceControl and not the endpoint.

Can you open a separate issue for it and elaborate on why the current implementation wouldn't work for you? Have you tried naming your endpoints like so?

[OranguTech]

@HEskandari - (I realize this is an older conversation)

I don't think so - this is about having human readable names in ServiceInsight, connecting to Service Control instances. See screenshot - which instance is that: Test1 that's part of our CI/CD path, a sandbox one that gets wiped every week, or Production?

I get the feeling that we must be set up in a way you're not expecting or missing some very important context, otherwise I'm mystified by the confusion or why this is much of a question on a long-term design decision - to me this is like asking why you'd want bookmarks/saved connections in a GUI SSH client, or why do we use DNS when ip addresses work just fine.