Splunk Search

Split Single columns in equal multiple columns

jerinvarghese
Communicator

Hi All,

I have a code, that gives below output.

CODE: 

| inputlookup ONMS_nodes.csv
| table nodelabel

OUTPUT : 

nodelabel
LANCUA005
LANCUA008
LANCUA012
LANCUA014
LANCUA016
LANCUA018
LANCUA019
LANCUA020
LANCUA022
LANCUA023

 

This is a sample output. List can goes more than 600 or 700 devices. 

Requirement is like : 

Can we split this into multiple columns within the panel.

nodelabelnodelabel
LANCUA005LANCUA016
LANCUA008LANCUA018
LANCUA012LANCUA019
LANCUA014LANCUA020
LANCUA023LANCUA022

 

SO that the content can be used the whole single panel  page to display the entire content.

Labels (6)
0 Karma
1 Solution

tscroggins
Champion

@jerinvarghese 

In SPL, you can count rows and columns and add xyseries to reformat by row/column:

| inputlookup ONMS_nodes.csv
| table nodelabel
| streamstats reset_after="rows==10" count as rows
| streamstats count as columns
| eval columns=floor((columns-1)/10)
| xyseries rows columns nodelabel
| sort rows
| fields - rows

 In this example, the columns (fields) are labeled 0, 1, 2, ..., 9. You can't give multiple fields the same label, but you can prefix them with "nodelabel" to make them a little more descriptive:

| inputlookup ONMS_nodes.csv
| table nodelabel
| streamstats reset_after="rows==10" count as rows
| streamstats count as columns
| eval columns=floor((columns-1)/10)
| xyseries rows columns nodelabel
| sort rows
| fields - rows
| foreach * [ rename <<FIELD>> as nodelabel_<<FIELD>> ]

 

View solution in original post

0 Karma

tscroggins
Champion

@jerinvarghese 

In SPL, you can count rows and columns and add xyseries to reformat by row/column:

| inputlookup ONMS_nodes.csv
| table nodelabel
| streamstats reset_after="rows==10" count as rows
| streamstats count as columns
| eval columns=floor((columns-1)/10)
| xyseries rows columns nodelabel
| sort rows
| fields - rows

 In this example, the columns (fields) are labeled 0, 1, 2, ..., 9. You can't give multiple fields the same label, but you can prefix them with "nodelabel" to make them a little more descriptive:

| inputlookup ONMS_nodes.csv
| table nodelabel
| streamstats reset_after="rows==10" count as rows
| streamstats count as columns
| eval columns=floor((columns-1)/10)
| xyseries rows columns nodelabel
| sort rows
| fields - rows
| foreach * [ rename <<FIELD>> as nodelabel_<<FIELD>> ]

 

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...