Add a config file example

[robsonpeixoto]

The current document are missing a config file example. Please add one.

[boly38]

while waiting for doc (agree that is missing :) ),

I just add here one sample found from #217

Seems that listen hostname must match "-host" parameter
please note that I'm not toxiproxy contributor (only end-user)

cat config/proxies.json
[
  {
    "name": "id_dev_http",
    "listen": "0.0.0.0:26080",
    "upstream": "myproxyfiedService:8080"
  }
]

[alexgvo]

Somebody know, can you add & assign toxics on proxies during startup of server? Using proxies.json?

[boly38]

(I've not done the test but ) @alexgvo did you try something similar to this sample (embedding toxics definiton) ?

{
    "tservice": {
        "name": "tservice",
        "listen": "[::]:9000",
        "upstream": "servicehost:8080",
        "enabled": true,
        "toxics": [
            {
                "attributes": {
                    "timeout": 0
                },
                "name": "serviceTimeout",
                "type": "timeout",
                "stream": "upstream",
                "toxicity": 1
            }
        ]
    },
    "tother": {
        "name": "tother",
        "listen": "[::]:9100",
        "upstream": "otherservice:8081",
        "enabled": true,
        "toxics": []
    }
}

[alexgvo]

(I've not done the test but ) @alexgvo did you try something similar to this sample (embedding toxics definiton) ?

{
    "tservice": {
        "name": "tservice",
        "listen": "[::]:9000",
        "upstream": "servicehost:8080",
        "enabled": true,
        "toxics": [
            {
                "attributes": {
                    "timeout": 0
                },
                "name": "serviceTimeout",
                "type": "timeout",
                "stream": "upstream",
                "toxicity": 1
            }
        ]
    },
    "tother": {
        "name": "tother",
        "listen": "[::]:9100",
        "upstream": "otherservice:8081",
        "enabled": true,
        "toxics": []
    }
}

Yes, I have tried the same construction...didn't work for me.

{
		"name": "proxy1",
		"listen": "0.0.0.0:8474",
		"upstream": "127.0.0.1:8080",
        "enabled": true,
		"toxics": [{
			"name": "toxic1",
			"type": "latency",
			"stream": "downstream",
			"toxicity": 1,
			"attributes": {
				"latency": 20,
				"jitter": 5
			}

		}]
	}

[boly38]

ok sorry then :| - in addition, I made a mistake using {} instead of [].
NB/ 8474 is already toxiproxy default port (maybe you should avoid this port for your listen directive)

• I've done test with /populate api, and toxics are not undertaken too.
• I've done test with -config proxies.json that includes proxy+toxics, and proxy is well defined but with empty toxics (That confirm your test)

[jpittis]

If you ping me on a PR to update the docs, it should be a quick turnaround to merge.

[KernelDeimos]

If anyone else finds this on Google like I did let me save you some time - adding toxics like this doesn't work right now.

• Add ability to specify toxics in the config file #447 describes where in the code toxics are excluded
• this PR vaguely describes a solution maybe I think