It wasn't clear if I should also configure the $SPLUNK_HOME/etc/apps/ta-bamboo/bin/config.ini, but I've done that as well just to be sure.
Is the config.ini required?
Unfortunately I can't see any data getting into Splunk. I've verified the connection between Splunk and Bamboo server is OK. There are the following details and errors in the log files:
2017-02-20 14:01:36,651 INFO 21 Bamboo server:https://[my bamboo server]:443
2017-02-20 14:03:43,997 ERROR 195 Failed on request: Traceback (most recent call last):
File "/opt/splunk/etc/apps/ta-bamboo/bin/bamboo.py", line 180, in getbambooplans
resp = requests.get(translatedurl, *args)
File "/opt/splunk/etc/apps/ta-bamboo/bin/libs/requests/api.py", line 67, in get
return request('get', url, params=params, *kwargs)
File "/opt/splunk/etc/apps/ta-bamboo/bin/libs/requests/api.py", line 53, in request
return session.request(method=method, url=url, *kwargs)
File "/opt/splunk/etc/apps/ta-bamboo/bin/libs/requests/sessions.py", line 468, in request
resp = self.send(prep, *sendkwargs)
File "/opt/splunk/etc/apps/ta-bamboo/bin/libs/requests/sessions.py", line 576, in send
r = adapter.send(request, **kwargs)
File "/opt/splunk/etc/apps/ta-bamboo/bin/libs/requests/adapters.py", line 437, in send
raise ConnectionError(e, request=request)
ConnectionError: HTTPSConnectionPool(host='[my bamboo server]', port=443): Max retries exceeded with url: /rest/api/latest/plan.json?max-results=1000 (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 110] Connection timed out',))
2017-02-20 14:03:44,273 INFO 21 Bamboo server:https://[my bamboo server]:443
2017-02-20 11:53:16,600 INFO pid=16220 tid=MainThread file=basemodinput.py:init:50 | Can not import package:libssetup_util
First, you can ignore: Can not import package:libssetuputil.
Second, I'm guessing you have your bamboo server in the cloud or a DMZ with firewall/NSG rules and your access is being denied.
This is the situation I was in and the errors I was seeing. Pointing splunk at a local squid proxy that went direct for everything else and via the enterprise proxy (whose source address was allowed to access the bamboo server) for bamboo solved my problem. Alternatively, it you have a proxy that can access everything your splunk needs to, you could just point splunk at the proxy.