Tracing properties do not seem to match ecs about ecs-dotnet HOT 2 CLOSED

OK, this looks like a limitation in the generator, but one could argue that it is also a quirk in the ECS schema definition.

The tracing root object is described with a prefix: '', the same as the base root object - on inspection these are the only two root objects defined with an empty string prefix.

I think it might make more sense for the schema to represent the trace and transaction object as either child objects on the base root, or to flatten the hierarchy by one level and have both trace and transaction exist as their own root objects. This would at least ensure that the schema is more consistent with itself.

In the meantime I will modify the generator to treat this object as described in the documentation and will raise an issue on the ecs repo.

from ecs-dotnet.

Ah yeah for simplicity's sake both IDs were added in the same file "tracing", but their key names should actually be "trace.id" and "transaction.id".

Relying on the key flat_name in either the nested or flat representation of ECS yaml files will get you the correct key names for fields (base fields are also quirky that way).

You should not rely on the nesting to construct the key name. Leave that mess to me :-)

Corollary, if you need more precomputed values in either yaml file, please let me know. I'll be happy to add them to the ECS generator :-)

from ecs-dotnet.