Splunk Search

tonumber command returns a null value

rphillips_splk
Splunk Employee
Splunk Employee

why does the tonumber command return a null value when the string being evaluated contains a space?

example:
string padded by a space character before the 1 returns null:
| stats count| eval test=" 1"|eval me=tonumber(test)

removing the padding returns a value:
| stats count| eval test="1"|eval me=tonumber(test)

workaround for strings with spaces:
| stats count| eval test=" 1"|eval me=trim(test)

Tags (4)
1 Solution

rphillips_splk
Splunk Employee
Splunk Employee

This has been identified as a bug and is targeted to be fixed in the 6.2.5 maintenance release (~Sept/Oct 2015)

View solution in original post

rphillips_splk
Splunk Employee
Splunk Employee

This has been identified as a bug and is targeted to be fixed in the 6.2.5 maintenance release (~Sept/Oct 2015)

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!

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Splunk Cloud Application Management in Terraform

Now On-Demand   We’re diving into how you can bring Infrastructure as Code (IaC) principles to your Splunk ...