Run formatter and update refcache

.htmltest.yml

@@ -34,3 +34,5 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
   - ^https://opentelemetry\.io/.
   # TODO: drop after fix to https://github.com/open-telemetry/opentelemetry.io/issues/2354
   - ^https://open-telemetry\.github\.io/opentelemetry-python/benchmarks/
+  # TODO: remove after merge of https://github.com/open-telemetry/opentelemetry.io/pull/2594
+  - ^https://elastic.co/blog/ecs-elastic-common-schema-otel-opentelemetry-announcement

.vscode/cspell.json

@@ -24,6 +24,7 @@
     "opentelemetry",
     "otel",
     "otelcol",
+    "OTEP",
     "otlp",
     "OTLP",
     "pluggable",

content/en/blog/2023/ecs-otel-semconv-convergence.md

@@ -1,10 +1,10 @@
 ---
-title: Announcing the Elastic Common Schema (ECS) and OpenTelemetry Semantic Convention Convergence
+title:
+  Announcing the Elastic Common Schema (ECS) and OpenTelemetry Semantic
+  Convention Convergence
 linkTitle: ECS and OTel SemConv Convergence
 date: 2023-04-17
-spelling:
-  cSpell:ignore Reiley Yang
-  cSpell:ignore ECS
+spelling: cSpell:ignore ECS Reiley SemConv Yang
 author: '[Reiley Yang](https://github.com/reyang)'
 ---
 
@@ -20,14 +20,14 @@ OpenTelemetry shares the same interest of improving the convergence of
 observability and security in this space. We believe this schema merge brings
 huge value to the open-source community because:
 
-* ECS has years of proven success in the logs, metrics, traces and security
+- ECS has years of proven success in the logs, metrics, traces and security
   events schema, providing great coverage of the common problem domains.
-* ECS provides schema for security domain fields, which is an important aspect
+- ECS provides schema for security domain fields, which is an important aspect
   of telemetry.
-* Converging two separate standards into one single standard will help to boost
+- Converging two separate standards into one single standard will help to boost
   the ecosystem (e.g. instrumentation libraries, tools and consumption
   experiences), which benefits both the telemetry producers and consumers.
-* This joint effort would benefit from domain experts across logging,
+- This joint effort would benefit from domain experts across logging,
   distributed tracing, metrics and security events. As a result, we expect to
   have more consistent signals across different pillars of observability and
   security events.
@@ -38,16 +38,13 @@ transition is critical for users. A dedicated OpenTelemetry Semantic Convention
 working group will be created with domain experts from both Elastic and
 OpenTelemetry joining. We're also welcoming domain experts who are passionate
 about data schemas and semantic conventions to join us. If you're interested in
-contributing, join our [OTel Semantic Conventions working
-group](https://github.com/open-telemetry/community#specification-sigs), and join
-the discussion on our [Slack
-channel](https://cloud-native.slack.com/archives/C041APFBYQP).
+contributing, join our
+[OTel Semantic Conventions working group](https://github.com/open-telemetry/community#specification-sigs),
+and join the discussion on our
+[Slack channel](https://cloud-native.slack.com/archives/C041APFBYQP).
 
 ## References
 
-* [Announcement from
-  Elastic](https://elastic.co/blog/ecs-elastic-common-schema-otel-opentelemetry-announcement)
-* [OpenTelemetry Semantic
-  Conventions](https://opentelemetry.io/docs/concepts/semantic-conventions/)
-* [OTEP 199: Merge Elastic Common Schema with OpenTelemetry Semantic
-  Conventions](https://github.com/open-telemetry/oteps/blob/d02a3e2e75dc934fb38c5db88eb41fbe85730af4/text/0199-support-elastic-common-schema-in-opentelemetry.md)
+- [Announcement from Elastic](https://elastic.co/blog/ecs-elastic-common-schema-otel-opentelemetry-announcement)
+- [OpenTelemetry Semantic Conventions](https://opentelemetry.io/docs/concepts/semantic-conventions/)
+- [OTEP 199: Merge Elastic Common Schema with OpenTelemetry Semantic Conventions](https://github.com/open-telemetry/oteps/blob/d02a3e2e75dc934fb38c5db88eb41fbe85730af4/text/0199-support-elastic-common-schema-in-opentelemetry.md)

static/refcache.json

@@ -219,6 +219,10 @@
     "StatusCode": 200,
     "LastSeen": "2023-02-15T20:41:03.78002-05:00"
   },
+  "https://cloud-native.slack.com/archives/C041APFBYQP": {
+    "StatusCode": 200,
+    "LastSeen": "2023-04-12T11:20:32.403714-04:00"
+  },
   "https://cloud-native.slack.com/archives/C0422FSELH0": {
     "StatusCode": 200,
     "LastSeen": "2023-02-15T20:40:32.32299-05:00"
@@ -1755,6 +1759,10 @@
     "StatusCode": 200,
     "LastSeen": "2023-02-20T08:15:28.84376-05:00"
   },
+  "https://github.com/open-telemetry/community#specification-sigs": {
+    "StatusCode": 200,
+    "LastSeen": "2023-04-12T11:20:27.134426-04:00"
+  },
   "https://github.com/open-telemetry/community/discussions/1203": {
     "StatusCode": 200,
     "LastSeen": "2023-02-20T08:04:49.421838-05:00"
@@ -2535,6 +2543,10 @@
     "StatusCode": 200,
     "LastSeen": "2023-02-20T08:04:55.176981-05:00"
   },
+  "https://github.com/reyang": {
+    "StatusCode": 200,
+    "LastSeen": "2023-04-12T11:20:10.566057-04:00"
+  },
   "https://github.com/riandyrn/otelchi": {
     "StatusCode": 200,
     "LastSeen": "2023-02-20T07:43:32.400852-05:00"
@@ -3895,6 +3907,10 @@
     "StatusCode": 200,
     "LastSeen": "2023-02-18T13:33:53.628417-05:00"
   },
+  "https://www.elastic.co/": {
+    "StatusCode": 200,
+    "LastSeen": "2023-04-12T11:20:16.022774-04:00"
+  },
   "https://www.elastic.co/guide/en/apm/get-started/current/open-telemetry-elastic.html": {
     "StatusCode": 206,
     "LastSeen": "2023-02-18T13:33:59.582146-05:00"
@@ -3907,6 +3923,10 @@
     "StatusCode": 206,
     "LastSeen": "2023-02-18T13:41:59.100249-05:00"
   },
+  "https://www.elastic.co/guide/en/ecs/master/ecs-reference.html": {
+    "StatusCode": 206,
+    "LastSeen": "2023-04-12T11:20:21.66934-04:00"
+  },
   "https://www.envoyproxy.io": {
     "StatusCode": 206,
     "LastSeen": "2023-02-18T13:44:26.91649-05:00"