Are you a member of the Splunk Community?
- Find Answers
- :
- Using Splunk
- :
- Splunk Search
- :
- curl fields order on export csv
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When running a curl for servicesNS/-/-/search/jobs/export -d search="savedsearch temp" -d output_mode=csv
I see that the fields do not output in the order as defined by the underlying search.
Conversely, when running the same curl, but removing the -d output_mode=csv, I see the fields output in the correct order.
Before opening a bug, I figured I'd check with the community. Has anyone seen this before? Known issue or by design?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, yes! So the answer is that the cosmetics of the search, in this case the field ordering, happen on the search UI. So it turns out the command line search doesn't do this formatting and therefore the field order is disregarded.
I highlighted that this is misleading. There is no warning to the user that they are attempting to use a command (fields, table) which will not have expected behavior.
I have case 190546 open for a feature request to "So that the order when using output=csv and the default xml output mode are consistent."
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, yes! So the answer is that the cosmetics of the search, in this case the field ordering, happen on the search UI. So it turns out the command line search doesn't do this formatting and therefore the field order is disregarded.
I highlighted that this is misleading. There is no warning to the user that they are attempting to use a command (fields, table) which will not have expected behavior.
I have case 190546 open for a feature request to "So that the order when using output=csv and the default xml output mode are consistent."
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good to know. Thanks.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@SloshBurch, did you get an answer from Splunk on this? I'm seeing a similar behavior.
Splunk Observability for AI
Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...
Splunk Observability as Code: From Zero to Dashboard
