@@ -19,7 +19,7 @@ namespace OpenTelemetry.Trace
     /// <summary>
     /// Defines well-known span attribute keys.
     /// </summary>
-    public static class SpanAttributeConstants
+    internal static class SpanAttributeConstants
     {
 #pragma warning disable CS1591 // Missing XML comment for publicly visible type or member
         public const string StatusCodeKey = "otel.status_code";
// <copyright file="SpanAttributeConstants.cs" company="OpenTelemetry Authors">
// Copyright The OpenTelemetry Authors
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//     http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
// </copyright>

namespace OpenTelemetry.Trace
{
    /// <summary>
    /// Defines well-known span attribute keys.
    /// </summary>
    public static class SpanAttributeConstants
    {
#pragma warning disable CS1591 // Missing XML comment for publicly visible type or member
        public const string StatusCodeKey = "otel.status_code";
        public const string StatusDescriptionKey = "otel.status_description";

        public const string HttpPathKey = "http.path";

        public const string DatabaseStatementTypeKey = "db.statement_type";

#pragma warning restore CS1591 // Missing XML comment for publicly visible type or member
    }
}

i am wondering why is the instrumentation populating those tags which are not part of semantic convention? we can eliminate that, and then eliminate the need for this at all. (Lets address it separately, Okay to merge this)