Read both the manual and the configuration file to learn about how to get the output/logging to suit your data analysis toolchain (look at -q, -v and the csv parameter). And the FAQ - there are different gems in each document.

Authenticating siege clients

If any of your webapp is protected by HTTP Basic Auth (i.e. the server returns
401 Not Authorized with WWW-Authenticate header), then you can configure siege
to authenticate using the login parameter in the configuration ~/.siegerc:

login = username:password[:realm]

If however, your webapp uses form-based authentication, look into the config file. There is a parameter 'login-url', undocumented elsewhere, which allows every siege client to login to the webapp and establish a session. This URL will be hit once for each
siege client session:

login-url = http://my.example.com/login POST name=me&password=abc123

This makes siege much more useful.

Running a siege with bombard

Make sure you have 2 perl modules: GD and Chart::Lines, then build/install bombard.