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
Get Updates on the Splunk Community!

Optimize Cloud Monitoring

  TECH TALKS Optimize Cloud Monitoring Tuesday, August 13, 2024  |  11:00AM–12:00PM PST   Register to ...

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...

Stay Connected: Your Guide to July and August Tech Talks, Office Hours, and Webinars!

Dive into our sizzling summer lineup for July and August Community Office Hours and Tech Talks. Scroll down to ...