Avalanche on EC2, SP_SIM_TIME Key not found

For engineers Collectors
1

Hey,

I am running avalanche on an EC2 instance and I am following all the steps as described in the documentation: https://github.com/snowplow/avalanche

I export all the variables needed for running the test to my bashprofile:

export SP_COLLECTOR_URI=my-collector-endpoint.com
export SP_SIM_TIME=5
export SP_BASELINE_USERS=100
export SP_PEAK_USERS=250

printenv will show me the variables.
However, when I run the following command:

sudo /home/ubuntu/snowplow/gatling/gatling-charts-highcharts-bundle-2.2.1-SNAPSHOT/bin/gatling.sh -sf /home/ubuntu/snowplow/src -s com.snowplowanalytics.avalanche.ExponentialPeak

I get the following error message:

Exception in thread "main" java.util.NoSuchElementException: key not found: SP_SIM_TIME
	at scala.collection.MapLike$class.default(MapLike.scala:228)
	at scala.collection.AbstractMap.default(Map.scala:59)
	at scala.collection.MapLike$class.apply(MapLike.scala:141)
	at scala.collection.AbstractMap.apply(Map.scala:59)
	at com.snowplowanalytics.avalanche.ExponentialPeak.<init>(ExponentialPeak.scala:48)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at java.lang.Class.newInstance(Class.java:442)
	at io.gatling.app.Gatling$.io$gatling$app$Gatling$$$anonfun$1(Gatling.scala:41)
	at io.gatling.app.Gatling.run(Gatling.scala:92)
	at io.gatling.app.Gatling.runIfNecessary(Gatling.scala:75)
	at io.gatling.app.Gatling.start(Gatling.scala:65)
	at io.gatling.app.Gatling$.start(Gatling.scala:57)
	at io.gatling.app.Gatling$.fromArgs(Gatling.scala:49)
	at io.gatling.app.Gatling$.main(Gatling.scala:43)

What am I doing wrong? Btw, is there a docker image publicly available for the avalanche ami? I would like to run avalanche in a customised container.

2

Perhaps try running with sudo -E to preserve your environment variables? I suspect they aren’t being preserved if you are exporting them as a non-root user.

1 Like
3

Thanks. It worked.