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)

Get Updates on the Splunk Community!

See your relevant APM services, dashboards, and alerts in one place with the updated ...

As a Splunk Observability user, you have a lot of data you have to manage, prioritize, and troubleshoot on a ...

Index This | What goes away as soon as you talk about it?

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

What's New in Splunk Observability Cloud and Splunk AppDynamics - May 2025

This month, we’re delivering several new innovations in Splunk Observability Cloud and Splunk AppDynamics ...