Allow the configuration of distributed tracing to be disabled

[ritzorama]

Current Behavior

Currently, while running Meshery Server, I see the following debug logs:

14:20:07 traces export: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:4317: connect: connection refused"

I have not defined a trace collector in my local deployment.

Desired Behavior

I would like to be able to disable tracing in deployments without a defined collector target. These logs are unnecessary noise, when no collector is present.

Implementation

1. Both github.com/meshery/meshkit AND github.com/meshery/meshery will need to be enhanced with this configurable deployment option.
2. Support an environment variable for Meshery deployments.
3. Ensure that this deployment option is exposed in Meshery's Helm chart values.yaml, too.

Acceptance Tests

• 1. Unless, trace collector target is configured, don't attempt to connect to collector.
• 2. The appropriate installation / deployment pages in Meshery Docs are updated.

---

Contributor Guides and Handbook

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Meshery UI in Figma
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[welcome]

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Contributors' Welcome Guide, engage in the discussion forum, and be sure to join the community Slack.

[iamgoeldhruv]

@ritzorama I would like to take this issue.
Can you assign it to me.