All Apps and Add-ons

Splunk DB Connect 2.1.1: Why is "shortnames = t" not preventing the renaming of columns?

NaraSplunk
Explorer

I'm having trouble getting the results of a database query to not rename the columns. In the documentation, it suggests that you can use "shortnames" to ask it not to rename the columns, but DBConnect seems to be ignoring that parameter.

Here's the request:

| dbxquery shortnames=t connection=c query="select date(s.date) as date, count as node_count from category_stats s where s.category_id=9 and s.stat_value='valid' and s.stat_name='node-count' order by date desc limit 50"

Here's the response:

{ 
     (001) NULL.date.DATE:  2016-02-01 
     (002) category_stats.node_count.INT:  25339 
  }

We are using Splunk 6.3.0 and Splunk DB Connect 2.1.1.

0 Karma
1 Solution

NaraSplunk
Explorer

Oh! Our mistake. It doesn't change the JSON that comes back, but it does change how those names get parsed and how they can be used in the rest of the query.

View solution in original post

0 Karma

NaraSplunk
Explorer

Oh! Our mistake. It doesn't change the JSON that comes back, but it does change how those names get parsed and how they can be used in the rest of the query.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...