Artillery: multiple targets

[monzerhijazi]

I have a scenario where I'm load testing 3 connected web applications (with one that provides a logged in session cookie) Is there any way to have one test file that can have multiple targets? I tried setting the URL on each request and not providing a target at all and that didn't work.

What I was thinking of doing:

config:
phases:
- duration: 1
arrivalRate: 1
defaults:
headers:
x-my-service-auth: '987401838271002188298567'

scenarios:

• flow:
  
  
  
  • get:
    
    url: "https://artillery.io/docs"
  
  
  • get:
    
    url: "https://anotherwebapp.com"
  
  

[benlipp]

Also need this functionality

[hassy]

You should be able to set target to one of the targets and then use full URLs in actual request specs.

[Cristy94]

What about WebSocket? How can I have multiple targets (eg: connect to one auth server, after auth responds with login info connect to the actual content server while using the ws engine?

[rtorrero]

There is a dirty workaround for this:
target: "http:/"
....
scenarios:

• flow:
  
  
  
  • get:
    
    url: "/server1:1234/test"
  
  
  • get:
    
    url: "/server2:4567/test2"
  
  

It's not ideal but it should work

[xuan9230]

Do we still need this workaround in 2019?

[itsmepetrov]

Faced with the same issue, workaround works, but it would be really good to see official solution for that

[mrmachine]

I also need this for an app with multiple websocket servers.

[brunettia]

Can you use HTTP and WS in the same file ?

[cshen4]

I have the same problem where my web application needs to connect to both http requests and a websocket. Is there a way to configure both https and wss requests in the same file?

[msarzijr]

I also would like to execute one test for WS and HTTP in the same configuration file and the environment config too.