MeshxRpc.attach_telemetry

You're seeing just the function attach_telemetry, go back to MeshxRpc module for more information.
Link to this function

attach_telemetry(telemetry_prefix, id \\ nil)

View Source

Specs

attach_telemetry(telemetry_prefix :: [atom()], id :: term()) :: :ok

Attaches pretty-printing Logger handler to telemetry events.

First argument should correspond to :telemetry_prefix configuration option described earlier. Second argument is telemetry handler id. If handler id is undefined it will be assigned value equal to second list element in telemetry_prefix.

Errors are logged with :error Logger level, all other events are logged with :debug level.

Example log of :ping call request:

Example2.Client.call(:ping)
12:17:11.869 [debug]
[:example2, Example2.Client, :call, :ping] -> :ok
local: %{conn_ref: "e9sJqA", node_ref: "nonode@nohost", svc_ref: "Elixir.Example2.Client"}
remote: %{conn_ref: "QglsBQ", node_ref: "nonode@nohost", svc_ref: "Elixir.Example2.Server"}
address: {:tcp, {127, 0, 0, 1}, 65535}
meta: [hsk_ref: 4034, req_ref: 4066, socket: #Port<0.14455>, state: :reply]
t_req: 2.152 [dser: 0.006, exec: 2.002, recv: 0.036, send: 0.105, ser: 0.003]
t_idle: 17547.272
size: [recv: "31B", send: "31B"]
blocks: [recv: 1, send: 1]

t_req is a total request time followed by [individual request steps times], milliseconds.

t_idle is a worker idle time, milliseconds.

attach_telemetry/2 is created as helper for use during development phase, most probably should not be used in production.