# No .Net logging library with recent ECS format available
**URL:** https://discuss.elastic.co/t/no-net-logging-library-with-recent-ecs-format-available/301301
**Category:** APM
**Tags:** ecs-elastic-common-schema, dotnet
**Created:** [April 1, 2022, 9:52am UTC](https://discuss.elastic.co/t/no-net-logging-library-with-recent-ecs-format-available/301301 "2022-04-01T09:52:21Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@nugroho-expereo](https://discuss.elastic.co/u/nugroho-expereo)
#### Post date: [April 1, 2022, 9:52am UTC](https://discuss.elastic.co/t/no-net-logging-library-with-recent-ecs-format-available/301301/1 "2022-04-01T09:52:21Z")
Hi,
.Net library for logging ([GitHub - elastic/ecs-dotnet: .NET integrations that use the Elastic Common Schema (ECS)](https://github.com/elastic/ecs-dotnet) ) seems to be unmaintained or abandoned. The last release was in June 2021 with ECS version 1.5 which is quite old.
We have a requirement to populate service.environment field that is available in the recent ECS and also used by APM.
Maybe it is good for Elastic to merge the project to apm-agent-dotnet that is more active and this will be inline with OpenTelemetry project 🙂 They have logs, metrics, and trace in one project ([GitHub - open-telemetry/opentelemetry-dotnet: The OpenTelemetry .NET Client](https://github.com/open-telemetry/opentelemetry-dotnet))
Is there any other alternative other than writing our own object model and transformation logic?
Thank you.
Regards,
Nugroho
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 22, 2022, 5:52am UTC](https://discuss.elastic.co/t/no-net-logging-library-with-recent-ecs-format-available/301301/2 "2022-04-22T05:52:23Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.