googlecloudplatform/opentelemetry-operator-sample

Toolbox of recipes, samples, and guides for using the OpenTelemetry Operator on Google Cloud

opentelemetry-operator-sample's Issues

Error on exporting Metrics to Google Cloud

There seems to be a problem with the metric exporter. On following the guide for exporting metrics to Google Cloud, I was facing the following error.

Collector version

0.75.0

Environment information

Environment

GKE

OpenTelemetry Collector configuration

apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: otel
spec:
  image: otel/opentelemetry-collector-contrib:latest
  config: |
    receivers:
      otlp:
        protocols:
          grpc:
          http:
    processors:
    exporters:
      googlecloud:
        metric:
          create_service_timeseries: true
          use_insecure: true
          prefix: "eevee"
      logging:
        loglevel: debug
    service:
      pipelines:
        traces:
          receivers: [otlp]
          processors: []
          exporters: [googlecloud]
        metrics:
          receivers: [otlp]
          processors: []
          exporters: [googlecloud]

Log output

│ 2023-04-17T09:42:48.503Z    info    service/telemetry.go:90    Setting up own telemetry...                                                                                                                                                                                   │
│ 2023-04-17T09:42:48.503Z    info    service/telemetry.go:116    Serving Prometheus metrics    {"address": ":8888", "level": "Basic"}                                                                                                                                         │
│ Error: failed to build pipelines: failed to create "googlecloud" exporter for data type "metrics": no project set in config, or found with application default credentials                                                                                                   │
│ 2023/04/17 09:42:48 collector server run finished with error: failed to build pipelines: failed to create "googlecloud" exporter for data type "metrics": no project set in config, or found with application default credentials

Also, please consider adding recipes for exporting metrics to Google Cloud.

Thank You!

Implementation of a "Kubernetes Operator" on .NET project

I appreciate if someone can share example that works on .net

Generate table of contents in readmes

Similar to GoogleCloudPlatform/opentelemetry-collector-builder-sample#18, we should generate the table of contents for the main readme and subdirectory readmes in the sample-apps and recipes folders. This generation should be verified in a presubmit for new PRs

Can't start collector - failed to call webhook - context deadline exceeded

This is a problem in GKE Autopilot cluster version 1.25.6-gke.1000.

I follow the guide from https://github.com/GoogleCloudPlatform/opentelemetry-operator-sample#prerequisites.

I installed cert-manager and OpenTelemetry Operator.
I can't start collector, here is the error:

$ kubectl apply -f collector-config.yaml 
Error from server (InternalError): error when creating "collector-config.yaml": Internal error occurred: failed calling webhook "mopentelemetrycollector.kb.io": failed to call webhook: Post "https://opentelemetry-operator-webhook-service.opentelemetry-operator-system.svc:443/mutate-opentelemetry-io-v1alpha1-opentelemetrycollector?timeout=10s": context deadline exceeded

Add diagrams

For the samples, recipes, and even basic install, it would be nice to have diagrams so users can visualize the end state of each one.

Service Account

I have followed this but there is no place to assign the serviceaccount otel-collector to the config. In the example, it's just annotating the namespace. I get permission denied in my deployment.

adding serviceAccount: "otel-collector" doesn't help.

2022/10/21 13:41:11 failed to export to Google Cloud Trace: rpc error: code = PermissionDenied desc = The caller does not have permission

I also changed the role to admin and no luck.

Sidecar-based resource detection recipe

Add a recipe to build on the basic resource detection recipe using multiple sidecar collectors that report to a centralized collector service for exporting. Demonstrate auto-instrumentation across multiple namespaces and languages (#19)

Logging exporters should use logLevel: debug

This lets users see the contents of logged spans (e.g. attributes)

Locations:

• https://github.com/GoogleCloudPlatform/opentelemetry-operator-sample/blob/86f2b4dc7bda79c818baedb47a2411c898c423a9/collector-config.yaml
• https://github.com/GoogleCloudPlatform/opentelemetry-operator-sample/blob/cfebc471e1eb48e2ec9d0f97b553dbf0aea2bd85/recipes/cloud-trace/collector-config.yaml

Define thorough operator integration test plan

Come up with a test/CI plan for making sure our recipes work on GKE (and with other GCP components)

Include cross-language samples

Use a combination of the existing samples to provide a walkthrough for deploying a multi-lingual sample, for example using the NodeJS client and Java server. Add a recipe to auto-instrument an app like this

Add Go sample project

Need a basic Go project following at least the client/server model of the other apps. This could be extended to show manual instrumentation or used in demos with auto-instrumentation (once it is available for Go)

Language sample apps should include a call to action at the end

Let me know what I should do once i've installed one. It should probably link to the recipes and tell me to try one out. Or it could assume users are using the "base" example, and show how to look at that applications' spans in the collector logs.

Provide links to cloud trace UI from example

It currently says: "Once the Collector restarts, you should see traces from your application". In the cloud trace example: https://github.com/GoogleCloudPlatform/opentelemetry-operator-sample/tree/main/recipes/cloud-trace

We should link to console.cloud.google.com/traces/list.

Sample for Operator auto-instrumentation with Go

Do you have any predictions for auto instrumentation with GO using GKE/ASM?