Proposal: Change duration to be microseconds

[watson]

Today the duration property is in milliseconds, but can represent microseconds using decimals:
1.234ms = 1234us

In the new intake API (v2), we change the timestamp properties to be an integer representing the number of microseconds since January 1, 1970 00:00:00 UTC.

I feel it would therefore be confusing to keep duration a milliseconds property.

@elastic/apm-server @elastic/apm-agent-devs Please vote on the following two questions:

Let's change duration to be in microseconds (at some point)

• APM Server
• RUM agent
• Node.js agent
• Python agent
• Ruby agent
• Java agent
• Go agent

Our team have time to implement this change before API v2 (or it doesn't affect the team)

• APM Server
• RUM agent
• Node.js agent
• Python agent
• Ruby agent
• Java agent
• Go agent

[mikker]

Very clear description of the issue and what voting means and entails 👏

[alvarolobato]

We all agree that it would be good having this change in V2, but this is a last minute change and not all agents are going to have time to do it. Not having all the agents with this change in before FF is an additional risk on top of the ones we already have. We will defer to another release.