Updating telemetry documentation for new helper framework (#59)

Updating telemetry docs for new framework

Author: ryanuber

website/docs/cloud-docs/agents/logging.mdx

@@ -76,9 +76,9 @@ internal URLs, and other sensitive material.
 Flash Messages are a type of log that HashiCorp may send to agents from time to time. These messages may be used to communicate important or breaking changes to the agent. Flash Messages will be emitted when HashiCorp adds a new one, or when starting up an agent for the first time. Their output looks something like:
 
 ```
-2021-09-22T15:20:59.269Z [WARN] core.notice: A breaking change is incoming.
+2021-09-22T15:20:59.269Z [WARN] notice: A breaking change is incoming.
 ```
 
 Flash Messages are version specific, and may only apply to the specific version of the agent you are running.
 
-Adding monitoring and alerting for these `core.notice` messages may help you operate Terraform Cloud Agents more easily.
+Adding monitoring and alerting for these `notice` messages may help you operate Terraform Cloud Agents more easily.

website/docs/cloud-docs/agents/metrics.mdx

@@ -38,7 +38,7 @@ Terraform Cloud agents emit three types of metric data:
 
 The following metrics are generated by the Terraform Cloud Agent core program,
 and are related to generic operations performed regularly by all agents. All
-metrics in this section are prefixed by `tfc-agent.`.
+metrics in this section are prefixed by `tfc-agent.core.`.
 
 | Meric name | Type | Description |
 | ---------------------------- | ----- | -------------------------------------------------------------------- |
@@ -59,7 +59,7 @@ processes (such as the Terraform binary or other programs) which maintain their
 own distinct runtimes and consume resources independently of the agent. To
 monitor resource utilization comprehensively, consider monitoring VM or
 container metrics. All metrics in this section are prefixed by
-`tfc-agent.runtime.`.
+`tfc-agent.core.runtime.`.
 
 | Metric name | Type | Description |
 | ------------------------------- | ----- | --------------------------------------------------- |
@@ -81,7 +81,7 @@ container metrics. All metrics in this section are prefixed by
 
 The following metrics are emitted by the `terraform` component, which is
 responsible for handling Terraform operations like plans and applies. All
-metrics in this section are prefixed by `tfc-agent.terraform.`.
+metrics in this section are prefixed by `tfc-agent.core.terraform.`.
 
 | Metric name | Type | Description |
 | ---------------------------------------------- | ----- | ----------------------------------------------------------------------------------- |
@@ -136,7 +136,7 @@ metrics in this section are prefixed by `tfc-agent.terraform.`.
 
 The following metrics are emitted by the `policy` component, which is
 responsible for handling OPA policy enforcement operations. All metrics in this
-section are prefixed by `tfc-agent.policy.`.
+section are prefixed by `tfc-agent.core.policy.`.
 
 | Metric name | Type | Description |
 | ---------------------------------------------- | ----- | -------------------------------------------------------- |

website/docs/cloud-docs/agents/tracing.mdx

@@ -8,16 +8,21 @@ description: >-
 
 The agent emits tracing spans that can be consumed by various distributed
 tracing tools. Information about supported tools can be found on the
-[OpenTelemetry Registry](https://opentelemetry.io/registry/). A span is a
-single unit of work performed by the agent.
+[OpenTelemetry Registry](https://opentelemetry.io/registry/). A span describes
+a single, concise unit of work performed by the agent, such as writing a file
+or downloading an artifact.
 
-Spans conform to the following rules:
+## Span names
 
-* Each span has a unique name in plain English, explaining what it represents.
- Due to this descriptive nature of spans, individual trace spans are not
- documented on this page.
-* Span attributes will be made up of sections, separated by periods. Sections
- will contain only alphanumeric characters and underscores.
- For example: `run.terraform_version`.
-* Span attributes in the `debug` namespace will have information relevant to
- the current span's scope.
+Each span has a unique name in plain English, explaining what it represents.
+Due to this descriptive nature of spans, individual trace spans are not
+documented on this page.
+
+## Span attributes
+
+Span attribute keys typically contain only letters, numbers, and underscores.
+In some cases, span attributes may contain dots (`.`) to provide structure to a
+set of related attributes.
+
+Span attributes in the `debug` namespace will have information relevant to the
+current span's scope.