Idea ID: 2877317

Use Application Name instead of Port from VTS

Status: Accepted

Backlog item for a future release.

See status update history

Currently, we're using port numbers to identify and route traffic to our various applications. While this approach has served us well, it can become cumbersome to manage, especially as we scale and add more services.

To address this, I suggest that we transition from using port numbers to using application names as identifiers. Instead of specifying port numbers, we can use clear and intuitive application names to access our services. This change not only streamlines our configuration but also makes it easier for team members to work with our services.

Here's how it would work:

  • Each application will have a unique name.
  • We'll maintain a mapping of these application names to their corresponding ports and internal service addresses.
  • Nginx, our web server, will be configured to route traffic to the appropriate service based on the provided application name.

This transition will simplify our server configuration and improve the accessibility of our services, making it easier for team members to interact with different applications.

Tags:

  • Hi  
    Yes i am looking for the same, but i agree with  on extending the server argument which will help us more.

  • Hi ,

    I agree with your proposal, but I like to request also for extending the "Server" argument to accept a longer URL:

    lrvtc_connect_ex("Server=">https://server/VTS-US", "InstName=MY_PROJECT1", ..., LAST);

    or even with port-number in URL

    lrvtc_connect_ex("Server=">https://server:8080/VTS-US", "InstName=MY_PROJECT1", ..., LAST);

    The use of the extended Server argument implies that we can access VTS via internal refers proxy and route to various VTS servers in multiple AWS regions. The configuration is then of cause not part of VTS's setup but that is OK. When an real Nginx is used by VTS it might be manually configured to do nice things as well.

    Let me know what you think.

    How to ask questions

    Reward contributions via likes or 'verified answers'

  • Hi Pavan, 

    Could you please confirm if below make sense to you?
    add a new argument ("InstName") for lrvtc_connect_ex, when port forwarding enabled and InstName set, something like"">https://server/instname=xyz" will be sent to Nginx, in this way, we can map instance name to port  in Nginx side, then tunnel the request to target server.

  • @David McLeish,

    Can you confirm that with option 1 it is also possible to use an more complex URL? We have a proxy server to access VTS UI in AWS and use:
    https://server/VTS-eu and https://server/VTS-us to access different VTS servers in AWS. Having this access path also for the VTS API (lrvts_connect_ex) would be great. Supporting the format https://server/VTS-us/APPLICATION

    I think that this is more than your option 1 proposal, because you want to give VTS nginx capabilities, but at least I like support for access via a reverse proxy for both UI and API.

    How to ask questions

    Reward contributions via likes or 'verified answers'

  • Thanks David for accepting the Idea, we look forward to the new release.