Cijo Thomas

All criterion from https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#becoming-a-maintainer is satisfied, merging. The person being nominated has accepted the nomination by approving the pull request - Done All maintainers have approved the pull request OR...

Welcome @utpilla to @open-telemetry/rust-maintainers !

Resource's support for schema_url is something that can be done purely in this repo. The one for Activity/Meter requires .NET runtime support, so better to track them separately.

> > Resource's support for schema_url is something that can be done purely in this repo. The one for Activity/Meter requires .NET runtime support, so better to track them separately....

> Is it eligible to be closed? Does some work not need to be done to use the new .NET 10 property? You are right. Some work still required in...

@cijothomas Could you describe how you implement this? `Activity` class is part of the .NET runtime repo, so it must be added there, not in this repo.

> Do you mean this capability to truncate would actually live in .Net itself and not it the SDK? Yes. SDK can contain the configuration, but it must be passed...

> Seeing logs dropped by my vendor due to the size of some exception messages. It’s unfortunate we cannot limit the attribute length. You can leverage this https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol#attribute-limits This issue...

There should be nothing specific about Azure Functions that prevent it from working there! If you can share a minimal repro, we can help find if there is any issue...

Ignore my above comment. There are no limits to LogRecord's body today, and that is a gap in the spec as well : https://github.com/open-telemetry/opentelemetry-specification/issues/4006