I used the --identity-prefix option in the liveki-cli load-test subcommand, but it doesn't take effect.
As shown below, the participant's identity should be prefixed with foo, but it is ignored and a random string called aejbl is prefixed.
$ livekit-cli load-test --verbose --room 1 --video-publishers 1 --subscribers 1 --identity-prefix foo
Using default project {}
URL: {}, api-key: {}, api-secret: {}
Starting load test with 1 video publishers, 1 subscribers, room: 1
2023/08/01 10:56:13 "level"=0 "msg"="received offer for subscriber"
2023/08/01 10:56:14 "level"=0 "msg"="received offer for subscriber"
2023/08/01 10:56:14 "level"=0 "msg"="ICE connected"
publishing simulcast video track - aejbl_pub_0
2023/08/01 10:56:14 "level"=0 "msg"="published simulcast track" "name"="video-simulcast" "source"="CAMERA"
2023/08/01 10:56:14 "level"=0 "msg"="successfully set publisher answer"
2023/08/01 10:56:14 "level"=0 "msg"="received offer for subscriber"
2023/08/01 10:56:15 "level"=0 "msg"="ICE connected"
Finished connecting to room, waiting 1000h0m0s
2023/08/01 10:56:15 "level"=0 "msg"="track subscribed" "participant"="aejbl_pub_0" "track"="TR_VCHPrH9do6BTnz" "kind"="video"
subscribed to track aejbl_1 TR_VCHPrH9do6BTnz video 1/1
noahlt
commented
1 year ago
I used the --identity-prefix option in the liveki-cli load-test subcommand, but it doesn't take effect. As shown below, the participant's identity should be prefixed with foo, but it is ignored and a random string called aejbl is prefixed.