Getting Data In

Large Decimal to Hex - Loss of Precision

pagaard
Observer

Greetings,

I would like to convert a large number to hex, just as described in this post.

While the above poster's issue was resolved via printf("%X",<field>), this did not work for me with a 19 digit uint64.

. Run-anywhere example:

 

| makeresults
| eval id="6932595798699158802"
| eval want="6035872600D42D12"
| eval dataHexUsingPrintf=printf("%X",id)
| table id want dataHexUsingPrintf

 

I've tried several combinations of exact(), tostring(id, "hex"), and all attempts fail, it appears due to a lack of precision in the initial conversion to 'number' type.

Example:

| makeresults
| eval id="6932595798699158802"
| convert num(id) as id_num
| eval want="6035872600D42D12"
| eval dataHexUsingPrintf=printf("%X",id_num)

Does Splunk support big num calculations of this type?
Is there a work around I'm missing to properly convert to hex?

 

Labels (1)
Tags (2)
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...