Analytics for schema files

[chalin]

Originally posted by @lmolkova in #3468:

let me bring it up on the semconv call tomorrow.

/cc @open-telemetry/specs-semconv-maintainers

A side question - @chalin do we have some stats on successful hits to schemas? E.g. I'd love to see a distribution of versions being requested, user-agents, etc?

I've started looking into this. Resources:

• https://docs.netlify.com/monitor-sites/site-analytics/
• https://hamatti.org/posts/showing-most-popular-posts-with-netlify-analytics/, to try at least for initial experimentation

[chalin]

@lmolkova @trask - FYI, /schemas/v1.13.0 is a 404 with 4.5K hits in the past month, so it seems that a lot of folks think that there's a "v" as part of the schema file name, which there is not as you know.

Interestingly, open-telemetry/opentelemetry-collector-contrib#22852 contains a reference to

"schemaUrl": "https://opentelemetry.io/schemas/v1.13.0",

Maybe that reference should be corrected so that folks don't get the wrong impression? Or worse, is that referring to a tool that is generating the invalid path? If so, the tool should be fixed if it hasn't already!

/cc @open-telemetry/specs-semconv-approvers

[lmolkova]

found it appearing in some old otel-dotnet versions https://github.com/open-telemetry/opentelemetry-dotnet/blob/303ab7a25a81d7804ac7414134366e61a9501114/src/OpenTelemetry.SemanticConventions/Resource/ResourceSemanticConventions.cs#L15, but it's no longer there.

I think we can't fix it without time machine.