The Container action lets you organize your other HTTP and Logic Actions and measure their collective response time. A container cannot have pre/post processors applied to it, if you place a processor in it, it will apply to all the other elements inside the container, according to the tree rules.
Containers will have statistics during the runtime, including response times, hits and all the usual metrics.
The response time of a container will be the sum of response times of all its children. Including subsets like the Download ressources option.
If any of a containers' children encounters an error, the container will also fail. Because of all this we strongly recommend using a different container for each action.
A good practice is to name your containers starting with numbers. This way sorting them by name will be relevant in the analysis.
The above setup will yield results like this: