fix: fixed the kubernetes instructions

[Calm-Rock]

Summary

Fixes the endpoint in Kubernetes environment instructions

Related Issues / PR's

#6192

---

Important

Updates Kubernetes instructions to use $(Otel-agent-IP) instead of localhost for endpoints in multiple language-specific documentation files.

• Behavior:
  • Updates Kubernetes instructions to replace localhost with $(Otel-agent-IP) in endpoint configurations across multiple language-specific documentation files.
  • Adds a note with a link to documentation for obtaining Otel-agent-IP in each file.
• Files Affected:
  • dotnet-kubernetes-instrumentApplication.md: Changes endpoint in Program.cs example.
  • elixir-kubernetes-instrumentApplication.md: Updates endpoint in runtime.exs configuration.
  • golang-kubernetes-runApplication.md: Modifies endpoint in Go run command.
  • ... and 10 other files for various languages including JavaScript, PHP, Python, Ruby, Rust, and Swift.

^{This description was created by for 2daab46. It will automatically update as commits are pushed.}

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 2daab46 in 38 seconds

More details

• Looked at 299 lines of code in 14 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. frontend/src/container/OnboardingContainer/Modules/APM/Dotnet/md-docs/Kubernetes/dotnet-kubernetes-instrumentApplication.md:47

• Draft comment:
  Ensure that the placeholder $(Otel-agent-IP) is correctly formatted for the specific context. For example, in shell scripts, use $Otel_agent_IP without parentheses. This issue is present in multiple files.
• Reason this comment was not posted:
  Comment did not seem useful.

2. frontend/src/container/OnboardingContainer/Modules/APM/Dotnet/md-docs/Kubernetes/dotnet-kubernetes-instrumentApplication.md:47

• Draft comment:
  Avoid hardcoding IP addresses directly in the code. Consider using a configuration file or environment variable to manage the Otel-agent-IP for better maintainability and consistency. This comment applies to similar instances in other documentation files as well.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable:
  The diff shows a change from a hardcoded IP address to a placeholder, which suggests that the author is already moving towards a more flexible solution. The comment might be redundant since the change aligns with the suggestion. However, the placeholder still implies a hardcoded value unless it's replaced by a configuration mechanism.
  The placeholder '$(Otel-agent-IP)' might still be considered a form of hardcoding if not properly managed through configuration. The comment could be relevant if the placeholder isn't linked to a configuration system.
  The comment is relevant if the placeholder is not connected to a configuration system, as it still represents a hardcoded value in the code.
  The comment is relevant because the placeholder '$(Otel-agent-IP)' might still be a hardcoded value if not managed through configuration.

Workflow ID: wflow_lnTCXRp1PbPEOmfu

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[prashant-shahi]

Can you use only .AddOtlpExporter() and rely on the environment variable OTEL_EXPORTER_OTLP_ENDPOINT for the Otel endpoint? (this goes as per the k8s-infra guide's send data section)

Also, use the http prefix as the insecure flag is applied based on this.

Ref: https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.OpenTelemetryProtocol/README.md#environment-variables

[prashant-shahi]

Please test and verify these instructions.

Data Flow:

Instrumented Application in K8s => K8s-Infra (Otel-Agent) => SigNoz OSS/Cloud