Splunk Search

Table does not display correct field spaces

antlefebvre
Communicator

When piping fields into a table, the table eliminates extra spaces inside the field.

For example:

person_name="Smith  MD, John" |table person_name
                  ^^ (Two Spaces)

returns

Smith MD, John
     ^ (One Space)

This is terrible for forms when going from a broad * search to a single name search as copy/paste returns no results.

How do I get a table to return the field with ALL spaces that were in the raw event?

Tags (1)
0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

The table command isn't to blame, it preserves the double space - HTML's wrapping of multiple spaces into one is to blame.

<tr class="shared-resultstable-resultstablerow" data-cid="view7405" data-view="views/shared/results_table/ResultsTableRow" data-row-index="0" data-render-time="0.001">
  <td data-cell-index="0">
    Smith  MD, John
  </td>
</tr>

As you can see, the double space has made it into the source code, but your browser correctly only renders one space.

You could in principle set the CSS property white-space: pre; for that cell/column, but this would make all the whitespace around the cell appear as well.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

The table command isn't to blame, it preserves the double space - HTML's wrapping of multiple spaces into one is to blame.

<tr class="shared-resultstable-resultstablerow" data-cid="view7405" data-view="views/shared/results_table/ResultsTableRow" data-row-index="0" data-render-time="0.001">
  <td data-cell-index="0">
    Smith  MD, John
  </td>
</tr>

As you can see, the double space has made it into the source code, but your browser correctly only renders one space.

You could in principle set the CSS property white-space: pre; for that cell/column, but this would make all the whitespace around the cell appear as well.

martin_mueller
SplunkTrust
SplunkTrust

The pedant in me would suggest that it's actually faulty data if there's more than one space in there. If your source agrees, you could set up an alert to get those responsible for the data to fix it on their end for greater overall quality - both in Splunk and in the source application.

0 Karma

antlefebvre
Communicator

Crap... thanks for the explanation.

0 Karma
Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...