Although this isn't the answer I was hoping to find, I appreciated the response nonetheless. It's frustrating that, rather than download an already created free app, my only option would now seem to be spending $3k+. I'll set this as the accepted solution however, as it would seem to be the only way to accomplish what I'm looking to do. Thanks for your time. ... View more

Thank you for the link! Ctrl+\ did the trick! ... View more

I'm running on Splunk 6.3.1 with DB Connect version 1.1.6, and DB Connect v2 version 2.1.0. Having the same issues you describe here. Did you ever find an answer to your question? ... View more

Has there been any progress made here? We're having the same issues on our system, and would really like to finish our upgrade from db connect 1 as soon as possible, as many of our tasks rely on database queries. ... View more

I'm on 2.0.4, so it's possible it could be something there, but that doesn't seem likely. One last idea would be to double-check the permissions on the .conf file. Other than that, I'm sorry I couldn't be of more help. ... View more

Assuming you did restart Splunk, then I'm fresh out of ideas.. What version of DB Connect are you running? ... View more

I would think that should work, although I didn't provide any hiddens= or other parameters, and just have a line with [*]. This will use the default stanza from the default directory. Did you restart Splunk after saving the conf file? ... View more

EDIT: Apparently this didn't resolve the issue.. It seemed to for awhile, but I am receiving the errors again. Please disregards the "solution" below. After editing bin/dbx2/health.py to log the actual exception rather than "The user [user] is not allowed to use the health logger." I was able to see the following: 11/13/2015 10:27:33 [WARNING] [health.py] [HTTP 404] https://127.0.0.1:8089/servicesNS/myUsername/splunk_app_db_connect/db_connect/health/myUsername; [{'type': 'ERROR', 'code': None, 'text': "In handler 'health': Could not find object id=myUsername"}] Navigating to the parent of this URL showed an 'admin' object, and a 'nobody' object. Doing some digging turned up healthlog.conf inside the default directory. Adding my username as a stanza (or * if you'd like everyone to have permission) to healthlog.conf inside the local directory stopped the error messages, and has seemed to resolve the issue. ... View more

Maybe the fact that you didn't add anything to the trustedIP in server.conf is what fixed it for you, believe it or not. I ended up resolving the issue when I realize that, unlike web.conf, server.conf's trustedIP only allows a single IP address. Removing the second IP address (leaving only localhost) from server.conf's trustedIP field resolved the issue for us. ... View more

After a lot of searching, I found that my issue was caused by the assumption that the click's provided field would be equal to $click.name$ like many other modules, but as I found here, the field is equal to the y-axis (equal to $click.name2 ). If your issue is similar to mine, changing the field="" line should resolve the issue. ... View more

Also having this issue.. Do charts not support the condition tag within drilldown? ... View more

+1 for requesting this feature. It seems odd that maps don't support this feature while others do. ... View more