New network and system fields

[jalvz]

Use case originated by RUM, see comment

Proposed fields

Optional fields, all agents

• metadata
• transaction context

Intake API field	Elasticsearch field	Elasticsearch Type
system.cpu.cores	system.cpu.cores	integer
system.memory.total	system.memory.total	long
network.effective_type	network.effective_type	keyword
network.rtt	network.rtt	integer
network.downlink	network.downlink	double
network.downlink_max	network.downlink_max	double
network.physical	network.physical	keyword

Optional fields, RUM only:

• transaction context

Intake API field	Elasticsearch field	Elasticsearch Type
page.saveData	page.saveData	boolean
page.servedViaServiceWorker	page.servedViaServiceWorker	keyword

system.cpu.cores and system.memory.total are aligned with corresponding Metricbeat fields, even if not in ECS.

If this proposal is approved, network.* fields will be proposed to ECS.

Vote

Agent	Yes	No	Indifferent	N/A	Link to issue
UI
Server					issues/3657
.NET
Go
Java
Node.js
PHP
Python
Ruby
RUM					pull/752

[axw]

I think none of the backend agents will send these fields, but it would be great to get some agreement nevertheless. @elastic/apm-agent-devs could you please take a look in the next week or so?

I think that system.memory.total could be very useful for serverless/lambda, where pricing is typically in "GB seconds". i.e. the cost is based on the amount of time your function runs, and the amount of provisioned memory. So it would be interesting for measuring the cost of running lambdas. CC @basepi

[felixbarny]

We already report system.memory.total as metrics: https://www.elastic.co/guide/en/apm/agent/java/current/metrics.html#metrics-system

Do you think backend agents should collect that metric on a per-transaction level, too?

[axw]

@felixbarny I haven't come across any use cases that would need that, so I don't think so.

[jalvz]

Hey there - I assume all backend agents will be indifferent, but can you tick boxes / raise comments?
Thanks!

[gregkalapos]

We already report system.memory.total as metrics: https://www.elastic.co/guide/en/apm/agent/java/current/metrics.html#metrics-system

Do you think backend agents should collect that metric on a per-transaction level, too?

Same on .NET, we also send system.memory.total (inspired by the Java agent), similarly only as a metric, not on transaction level.

[felixbarny]

We've talked about adding this to the RUM intake only. Is this still what's planned?

[jalvz]

yes! (as far as i know)

[jalvz]

So as everyone seems OK with this, I'll close and try to move forward.
Thanks all!