LSEG Data Library for .NET - Service Discovery always selects US East 1

I'm using the LSEG Data Library for .NET and I've noticed that the build-in Service Discovery mechanism always selects US East 1 when I create a session using the GetSession method. Usually it is "us-east-1-aws-3-med.optimized-pricing-api.refinitiv.net" to be specific.

I find that a bit odd since our own infrastructure is in AWS EU West.

Would it not be more optimal for Service Discovery to pick an endpoint in the EU?

Find more posts tagged with

.net

configuration

#technology

Accepted answers

All comments

Jirapongse

@KaareDB

Thank you for reaching out to us.

I will reach out to the product team and get back to you with the answer.

Jirapongse

@KaareDB

This could be done through the ld-data.config.json configuration file.

            "rdpSession": {
                "rdp-credentials": {
                    "app-key": "<Application Key>",

                    "password-grant": {
                        "machine-id": "<RDP Machine ID>",
                        "password": "<RDP Password>"
                    }
                },		
                "apis":{
                    "streaming":{
                        "pricing":{
                            "endpoints": {									
                                  "locations":["eu-west"]
                            }						
                        }
                    }
                }	
            },

The file must be in the working directory of the running application or set the location of the file in the LD_LIB_CONFIG_FILE environment variable.

lseg-data.config.zip

KaareDB

If I configure this will it still fall back to another endpoint if eu-west is unavailable?

And do you recommend I configure this or just leave it as is?

Jirapongse

If you would like to change the location to eu-west, you need to configure it.

Yes, it will fall back to other servers in eu-west.

EXPLORE OUR SITES