fix(content): correct code-block language tags and syntax errors

jstirnaman · jstirnaman · commit 0c0b78daf3a9 · 2026-06-30T17:06:53.000Z
Telegraf v1 plugin docs — label fixes so json/toml blocks parse
correctly under the CI linter:
- bind: named.conf syntax in json fence → text
- ctrlx_datalayer: ctrlX Datalayer source-value format → text
  (format unverified; upstream Telegraf PRs filed — see below)
- docker: TOML config snippets mislabeled as json → text
- jti_openconfig_telemetry: duplicate key in toml block → text
- opcua_listener, dynatrace: // inline comments in toml → #
- postgresql_extensible: backslash line continuation in toml → text
- win_eventlog: unclosed triple-quoted string in toml → text
- azure_data_explorer: KQL/Kusto code in json fence → text
- clarify: proprietary signal/values format in json fence → text
- elasticsearch: HTTP request + body in json fence → text
- zabbix: JSONL-format payloads in json fence → jsonl
- converter: unclosed toml string literal "unix → "unix"
- lookup, secretstore/http: ellipsis elide markers in json fence → text
- splunkmetric: valid JSON metric objects in javascript fence → json

InfluxDB Cloud / Cloud Serverless bucket docs:
- bucket-schema, create-bucket, update-bucket,
  manage-explicit-bucket-schemas: JSON API request bodies in
  javascript/js fences → json
diff --git a/content/influxdb/cloud/admin/buckets/bucket-schema.md b/content/influxdb/cloud/admin/buckets/bucket-schema.md
@@ -132,7 +132,7 @@ For example, the following request defines the _explicit_ bucket measurement sch
 
 {{< api-endpoint method="post" endpoint="https://cloud2.influxdata.com/api/v2/buckets/{BUCKET_ID}/schema/measurements" api-ref="/influxdb/cloud/api/buckets//-bucketID-/schema/measurements" >}}
 
-```js
+```json
 {
 	"name": "airSensors",
 	"columns": [
@@ -262,7 +262,7 @@ You can't modify or delete columns in bucket schemas.
 
     {{< api-endpoint method="patch" endpoint="https://cloud2.influxdata.com/api/v2/buckets/{BUCKET_ID}/schema/measurements/{MEASUREMENT_ID}" api-ref="/influxdb/cloud/api/bucket-schemas/" >}}
 
-    ```js
+    ```json
     {
       "columns": [
               {"name": "time", "type": "timestamp"},
diff --git a/content/influxdb/cloud/admin/buckets/create-bucket.md b/content/influxdb/cloud/admin/buckets/create-bucket.md
@@ -169,7 +169,7 @@ endpoint and set the `schemaType` property value to `explicit` in the request bo
 
 {{< api-endpoint method="post" endpoint="https://cloud2.influxdata.com/api/v2/buckets" api-ref="/influxdb/cloud/api/buckets/" >}}
 
-```js
+```json
 {
   "orgID": "{INFLUX_ORG_ID}",
   "name": "my-explicit-bucket",
diff --git a/content/influxdb/cloud/admin/buckets/update-bucket.md b/content/influxdb/cloud/admin/buckets/update-bucket.md
@@ -130,7 +130,7 @@ You can update the following bucket properties:
 
     {{< api-endpoint method="patch" endpoint="https://cloud2.influxdata.com/api/v2/buckets/{BUCKET_ID}" api-ref="/influxdb/cloud/api/buckets/" >}}
 
-    ```js
+    ```json
     {
       "name": "air_sensor",
       "description": "bucket holding air sensor data",
diff --git a/content/influxdb3/cloud-serverless/admin/buckets/manage-explicit-bucket-schemas.md b/content/influxdb3/cloud-serverless/admin/buckets/manage-explicit-bucket-schemas.md
@@ -151,7 +151,7 @@ You can't modify or delete columns in bucket schemas.
 
     {{< api-endpoint method="patch" endpoint="https://{{< influxdb/host >}}/api/v2/buckets/{BUCKET_ID}/schema/measurements/{MEASUREMENT_ID}" api-ref="/influxdb3/cloud-serverless/api/buckets/" >}}
 
-    ```js
+    ```json
     {
       "columns": [
               {"name": "time", "type": "timestamp"},
diff --git a/content/influxdb3/cloud-serverless/admin/buckets/update-bucket.md b/content/influxdb3/cloud-serverless/admin/buckets/update-bucket.md
@@ -119,7 +119,7 @@ You can update the following bucket properties:
 
     {{< api-endpoint method="patch" endpoint="https://{{< influxdb/host >}}/api/v2/buckets/{BUCKET_ID}" api-ref="/influxdb3/cloud-serverless/api/buckets/#operation/PatchBucketsID" >}}
 
-    ```js
+    ```json
     {
       "name": "air_sensor",
       "description": "bucket holding air sensor data",
diff --git a/content/telegraf/v1/data_formats/output/splunkmetric.md b/content/telegraf/v1/data_formats/output/splunkmetric.md
@@ -19,7 +19,7 @@ Th data is output in a format that conforms to the specified Splunk HEC JSON for
 [Send metrics in JSON format](http://dev.splunk.com/view/event-collector/SP-CAAAFDN).
 
 An example event looks like:
-```javascript
+```json
 {
   "time": 1529708430,
   "event": "metric",
@@ -104,7 +104,7 @@ Such as this example which overrides the index just on the cpu metric:
 You can use the file output when running telegraf on a machine with a Splunk forwarder.
 
 A sample event when `hec_routing` is false (or unset) looks like:
-```javascript
+```json
 {
     "_value": 0.6,
     "cpu": "cpu0",
diff --git a/content/telegraf/v1/input-plugins/bind.md b/content/telegraf/v1/input-plugins/bind.md
@@ -83,7 +83,7 @@ depending on your BIND version and configured statistics channel.
 Add the following to your named.conf if running Telegraf on the same host
 as the BIND daemon:
 
-```json
+```text
 statistics-channels {
     inet 127.0.0.1 port 8053;
 };
diff --git a/content/telegraf/v1/input-plugins/ctrlx_datalayer.md b/content/telegraf/v1/input-plugins/ctrlx_datalayer.md
@@ -321,7 +321,7 @@ Configuration:
 
 Source:
 
-```json
+```text
 "framework/metrics/system/memavailable-mb" : 365.93359375
 "framework/metrics/system/memused-mb" : 567.67578125
 ```
@@ -348,7 +348,7 @@ Configuration:
 
 Source:
 
-```json
+```text
 "alldata/dynamic/array-of-bool8" : [true, false, true]
 "alldata/dynamic/array-of-uint8" : [0, 255]
 ```
@@ -375,7 +375,7 @@ Configuration:
 
 Source:
 
-```json
+```text
 "motion/axs/Axis_1/state/values/actual" : {"actualPos":65.249329860957,"actualVel":5,"actualAcc":0,"actualTorque":0,"distLeft":0,"actualPosUnit":"mm","actualVelUnit":"mm/min","actualAccUnit":"m/s^2","actualTorqueUnit":"Nm","distLeftUnit":"mm"}
 "motion/axs/Axis_2/state/values/actual" : {"actualPos":120,"actualVel":0,"actualAcc":0,"actualTorque":0,"distLeft":0,"actualPosUnit":"deg","actualVelUnit":"rpm","actualAccUnit":"rad/s^2","actualTorqueUnit":"Nm","distLeftUnit":"deg"}
 ```
diff --git a/content/telegraf/v1/input-plugins/docker.md b/content/telegraf/v1/input-plugins/docker.md
@@ -165,7 +165,7 @@ for containers that have no explicit hostname set, as defined by docker.
 Kubernetes may add many labels to your containers, if they are not needed you
 may prefer to exclude them:
 
-```json
+```text
   docker_label_exclude = ["annotation.kubernetes*"]
 ```
 
@@ -174,7 +174,7 @@ may prefer to exclude them:
 Docker-compose will add labels to your containers. You can limit restrict labels
 to selected ones, e.g.
 
-```json
+```text
   docker_label_include = [
     "com.docker.compose.config-hash",
     "com.docker.compose.container-number",
diff --git a/content/telegraf/v1/input-plugins/jti_openconfig_telemetry.md b/content/telegraf/v1/input-plugins/jti_openconfig_telemetry.md
@@ -43,7 +43,7 @@ plugin ordering. See [CONFIGURATION.md](/telegraf/v1/configuration/#plugins) for
 
 ## Configuration
 
-```toml @sample.conf
+```text @sample.conf
 # Subscribe and receive OpenConfig Telemetry data using JTI
 [[inputs.jti_openconfig_telemetry]]
   ## List of device addresses to collect telemetry from
diff --git a/content/telegraf/v1/input-plugins/opcua_listener.md b/content/telegraf/v1/input-plugins/opcua_listener.md
@@ -586,9 +586,9 @@ This example group configuration shows how to use group settings:
      identifier = "5678"
 
     node_ids = [
-      {identifier="Sensor1"}, // default values will be used for namespace and identifier_type
-      {namespace="2", identifier="TemperatureSensor"}, // default values will be used for identifier_type
-      {namespace="5", identifier_type="i", identifier="2002"} // no default values will be used
+      {identifier="Sensor1"}, # default values will be used for namespace and identifier_type
+      {namespace="2", identifier="TemperatureSensor"}, # default values will be used for identifier_type
+      {namespace="5", identifier_type="i", identifier="2002"} # no default values will be used
     ]
 ```
 
diff --git a/content/telegraf/v1/input-plugins/postgresql_extensible.md b/content/telegraf/v1/input-plugins/postgresql_extensible.md
@@ -126,7 +126,7 @@ using the postgresql extensions [pg_stat_statements](http://www.postgresql.org/d
 * telegraf.conf postgresql_extensible queries (assuming that you have configured
  correctly your connection)
 
-```toml
+```text
 [[inputs.postgresql_extensible.query]]
   sqlquery="SELECT * FROM pg_stat_database"
   version=901
diff --git a/content/telegraf/v1/input-plugins/win_eventlog.md b/content/telegraf/v1/input-plugins/win_eventlog.md
@@ -147,7 +147,7 @@ There are three types of filtering: **Event Log** name, **XPath Query** and
 
 **Event Log** name filtering is simple:
 
-```toml
+```text
   eventlog_name = "Application"
   xpath_query = '''
 ```
diff --git a/content/telegraf/v1/output-plugins/azure_data_explorer.md b/content/telegraf/v1/output-plugins/azure_data_explorer.md
@@ -256,7 +256,7 @@ stored as dynamic data type, multiple ways to query this data-
    recommended performant way for querying over large volumes of data compared
    to querying directly over JSON attributes:
 
-  ```json
+  ```text
   // Function to transform data
   .create-or-alter function Transform_TargetTableName() {
         SourceTableName
diff --git a/content/telegraf/v1/output-plugins/clarify.md b/content/telegraf/v1/output-plugins/clarify.md
@@ -80,7 +80,7 @@ The following input would be stored in Clarify with the values shown below:
 temperature,host=demo.clarifylocal,sensor=TC0P value=49 1682670910000000000
 ```
 
-```json
+```text
 "signal" {
   "id": "temperature.value.TC0P"
   "name": "temperature.value"
diff --git a/content/telegraf/v1/output-plugins/dynatrace.md b/content/telegraf/v1/output-plugins/dynatrace.md
@@ -103,7 +103,7 @@ The endpoint for the Dynatrace Metrics API v2 is
   url = "https://{your-environment-id}.live.dynatrace.com/api/v2/metrics/ingest"
 
   ## API token is required if a URL is specified and should be restricted to the 'Ingest metrics' scope
-  api_token = "your API token here" // hard-coded for illustration only, should be read from environment
+  api_token = "your API token here" # hard-coded for illustration only, should be read from environment
 ```
 
 You can learn more about how to use the [Dynatrace API](https://docs.dynatrace.com/docs/shortlink/section-api).
diff --git a/content/telegraf/v1/output-plugins/elasticsearch.md b/content/telegraf/v1/output-plugins/elasticsearch.md
@@ -217,7 +217,7 @@ compatibility mode users need to set the `override_main_response_version` to
 
 On existing clusters run:
 
-```json
+```text
 PUT /_cluster/settings
 {
   "persistent" : {
@@ -228,7 +228,7 @@ PUT /_cluster/settings
 
 And on new clusters set the option to true under advanced options:
 
-```json
+```text
 POST https://es.us-east-1.amazonaws.com/2021-01-01/opensearch/upgradeDomain
 {
   "DomainName": "domain-name",
diff --git a/content/telegraf/v1/output-plugins/zabbix.md b/content/telegraf/v1/output-plugins/zabbix.md
@@ -186,7 +186,7 @@ measurement,host=hostname valueA=0,valueB=1
 
 It will generate this Zabbix metrics:
 
-```json
+```jsonl
 {"host": "hostname", "key": "telegraf.measurement.valueA", "value": "0"}
 {"host": "hostname", "key": "telegraf.measurement.valueB", "value": "1"}
 ```
@@ -200,7 +200,7 @@ measurement,host=hostname,tagA=keyA,tagB=keyB valueA=0,valueB=1
 
 Zabbix generated metrics:
 
-```json
+```jsonl
 {"host": "hostname", "key": "telegraf.measurement.valueA[keyA,keyB]", "value": "0"}
 {"host": "hostname", "key": "telegraf.measurement.valueB[keyA,keyB]", "value": "1"}
 ```
diff --git a/content/telegraf/v1/processor-plugins/converter.md b/content/telegraf/v1/processor-plugins/converter.md
@@ -143,7 +143,7 @@ Set the metric timestamp from a tag:
 [[processors.converter]]
   [processors.converter.tags]
     timestamp = ["time"]
-    timestamp_format = "unix
+    timestamp_format = "unix"
 ```
 
 ```diff
diff --git a/content/telegraf/v1/processor-plugins/lookup.md b/content/telegraf/v1/processor-plugins/lookup.md
@@ -75,7 +75,7 @@ added to a metric if the key matches.
 
 In the `json` format, the input `files` must have the following format
 
-```json
+```text
 {
   "keyA": {
     "tag-name1": "tag-value1",
@@ -136,7 +136,7 @@ Please note that empty tag-values will be ignored and the tag will not be added.
 
 With a lookup table of
 
-```json
+```text
 {
   "xyzzy-green": {
     "location": "eu-central",
diff --git a/content/telegraf/v1/secretstore-plugins/http.md b/content/telegraf/v1/secretstore-plugins/http.md
@@ -154,7 +154,7 @@ encryption section.
 
 Secrets are expected to be JSON data in the following flat key-value form
 
-```json
+```text
 {
     "secret name A": "secret value A",
     ...

Original file line number	Diff line number	Diff line change
`@@ -132,7 +132,7 @@ For example, the following request defines the _explicit_ bucket measurement sch`
`132`	`132`
`133`	`133`	`{{< api-endpoint method="post" endpoint="https://cloud2.influxdata.com/api/v2/buckets/{BUCKET_ID}/schema/measurements" api-ref="/influxdb/cloud/api/buckets//-bucketID-/schema/measurements" >}}`
`134`	`134`
`135`		-```js
	`135`	+```json
`136`	`136`	`{`
`137`	`137`	`"name": "airSensors",`
`138`	`138`	`"columns": [`
`@@ -262,7 +262,7 @@ You can't modify or delete columns in bucket schemas.`
`262`	`262`
`263`	`263`	`{{< api-endpoint method="patch" endpoint="https://cloud2.influxdata.com/api/v2/buckets/{BUCKET_ID}/schema/measurements/{MEASUREMENT_ID}" api-ref="/influxdb/cloud/api/bucket-schemas/" >}}`
`264`	`264`
`265`		- ```js
	`265`	+ ```json
`266`	`266`	`{`
`267`	`267`	`"columns": [`
`268`	`268`	`{"name": "time", "type": "timestamp"},`
Original file line number	Diff line number	Diff line change
@@ -169,7 +169,7 @@ endpoint and set the `schemaType` property value to `explicit` in the request bo
`169`	`169`
`170`	`170`	`{{< api-endpoint method="post" endpoint="https://cloud2.influxdata.com/api/v2/buckets" api-ref="/influxdb/cloud/api/buckets/" >}}`
`171`	`171`
`172`		-```js
	`172`	+```json
`173`	`173`	`{`
`174`	`174`	`"orgID": "{INFLUX_ORG_ID}",`
`175`	`175`	`"name": "my-explicit-bucket",`
Original file line number	Diff line number	Diff line change
`@@ -130,7 +130,7 @@ You can update the following bucket properties:`
`130`	`130`
`131`	`131`	`{{< api-endpoint method="patch" endpoint="https://cloud2.influxdata.com/api/v2/buckets/{BUCKET_ID}" api-ref="/influxdb/cloud/api/buckets/" >}}`
`132`	`132`
`133`		- ```js
	`133`	+ ```json
`134`	`134`	`{`
`135`	`135`	`"name": "air_sensor",`
`136`	`136`	`"description": "bucket holding air sensor data",`
Original file line number	Diff line number	Diff line change
`@@ -151,7 +151,7 @@ You can't modify or delete columns in bucket schemas.`
`151`	`151`
`152`	`152`	`{{< api-endpoint method="patch" endpoint="https://{{< influxdb/host >}}/api/v2/buckets/{BUCKET_ID}/schema/measurements/{MEASUREMENT_ID}" api-ref="/influxdb3/cloud-serverless/api/buckets/" >}}`
`153`	`153`
`154`		- ```js
	`154`	+ ```json
`155`	`155`	`{`
`156`	`156`	`"columns": [`
`157`	`157`	`{"name": "time", "type": "timestamp"},`
Original file line number	Diff line number	Diff line change
`@@ -119,7 +119,7 @@ You can update the following bucket properties:`
`119`	`119`
`120`	`120`	`{{< api-endpoint method="patch" endpoint="https://{{< influxdb/host >}}/api/v2/buckets/{BUCKET_ID}" api-ref="/influxdb3/cloud-serverless/api/buckets/#operation/PatchBucketsID" >}}`
`121`	`121`
`122`		- ```js
	`122`	+ ```json
`123`	`123`	`{`
`124`	`124`	`"name": "air_sensor",`
`125`	`125`	`"description": "bucket holding air sensor data",`