rmoff / shadowtraffic-examples

🚀 Example configuration files to help you get started.

ShadowTraffic examples

This repo contains runnable examples of how to use ShadowTraffic for common use cases.

Run each of these with:

docker run --env-file license.env -v $(pwd)/<configuration file>:/home/config.json shadowtraffic/shadowtraffic:latest --config /home/config.json --sample 10 --stdout --watch

• First steps
  • Hello world with Kafka
  • Hello world with Postgres
  • Hello world with a webhook
  • Hello world to Decodable
• Basic examples
  • The kitchen sink: Kafka retail data
  • The kitchen sink: Postgres retail data
  • Customers have a name, age, and membership level
  • 57% of votes are cast for Franklin Roosevelt
  • Transactions are uniformly priced between $2 and $200
  • Orders have a pre-existing customer
  • Support ticket messages arrive every 5000ms
  • Publish 80% of the tweets from 20% of the users
  • Send messages every 500 ms with a std dev of 40 ms
  • Place exactly 15 orders
  • Pick a date/timestamp between yesterday and tomorrow
  • 5 sensors whose value is the previous value plus a random number between -1 and 1
  • Telemetry data gets randomly delayed 10% of the time, discarded 2% of the time, and repeated 5% of the time
  • A stream of the h2o dataset configured for n=10M, k=10
  • An inventory of films are tracked in 100 stores, like the Sakila dataset
  • A new user comes online every 250ms and changes their IP every 1 second
  • 50 machines DDOSing EC2 instances in us-east-1 with ~200 byte packets every 10 ms
  • Suspicious accounts transacting that log in with a new IP address 1% of the time
  • 30 JVMs report their heap readings every 250 ms which oscillate around 50 mb
  • 200 merchants have their businesses audited once every ~25 days
  • Inventory is updated every 200ms and queries check its status every 500ms
• Advanced examples
  • 70% of all posts are from repeat users
  • Harvest customer IDs from Postgres for Kafka events
  • l Customers go through a 4-stage funnel
  • Debezium envelopes have 3 discrete states
  • 3 support agents field phone calls, arriving once a second
  • Flights take off every 5 seconds and report their geolocation
  • Every ~2 seconds, a new game is scheduled to start with bets placed every ~500ms
  • Bots post social content that get likes and shares only 5% of the time each