Splunk Search

Reordering columns not working through API

whateverwhouare
New Member

I want to reorder my columns. I tried both table and fields, and they seemed to work through the web UI, but when I tried it through the REST API the order did not change at all.

Is there any known problem with reordering through REST API, or can anyone point out what I'm doing wrong? Below is my query.

index=na1 host=*app* logRecordTypeseclk=1 earliest=-5h tableEnumOrId=Contact OR tableEnumOrId=CollaborationGroup | where rank < 10 | stats count by rank, tableEnumOrId | table count, tableEnumOrId, rank

EDIT:

I asked this a while ago but I think the issue is somehow stats is affecting table. When I change stats count by rank, tableEnumOrId to stats count by tableEnumOrId, rank, the output order changed accordingly. But no matter how I change the ordering of the column names in table, nothing changes.

Is this a known issue? Or am I just doing something wrong?

0 Karma

nicolas_perreau
Explorer

Hi!

I'm having the same issue with REST and I do not see anyway to fix it so far.

I've just upgraded from Splunk 5.0.5 to 6.2.2 and noticed the behavior.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...