Fixing error in config for internal-telemetry.md

[avilevy18]

Attempted to run collector-contrib with the example config posted on: https://opentelemetry.io/docs/collector/internal-telemetry/#self-monitoring

Found a few errors:

1. Collector failed with config error:

error decoding 'service.telemetry': decoding failed due to the following error(s):

'traces.processors': source data must be an array or slice, got map

• OTLP Exporter was trying to send with SSL, to receiver that was not set up with SSL.

warn	[email protected]/clientconn.go:1379	[core] [Channel #1 SubChannel #8]grpc: addrConn.createTransport failed to connect to {Addr: "127.0.0.1:14317", ServerName: "localhost:14317", }. Err: connection error: desc = "transport: authentication handshake failed: tls: first record does not look like a TLS handshake"	{"grpc_log": true}

Adding http:// before localhost in the exporters endpoint, enforces an insecure connection.

Attempted to use insecure: true option but nothing happened.

   traces:
      processors:
      - batch:
          exporter:
            otlp:
              protocol: grpc/protobuf
              endpoint: localhost:14317
              insecure: true

The insecure config options doesn't seem to do anything:
https://github.com/open-telemetry/opentelemetry-collector/blob/f74890a3889a82f57b839a8b316bb43b1e55f53e/service/telemetry/internal/otelinit/config.go#L216

[linux-foundation-easycla]

• ❌ - login: @avilevy18 . The commit (1bbca3a) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[tiffany76]

Hi @avilevy18, could you sign the CLA please?

@open-telemetry/collector-approvers, FYI.