Assigned
Status Update
No update yet.
Comments
ch...@google.com
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
ac...@trauzzi.me
Hello! Sorry to bring up this issue after almost a year but I wanted to add that we have chosen metric identifier as agent.googleapis.com/memory/percent_used but autoscaling didnt work out for us either. It would be appraciated if you can guide us.
ch...@google.com
Hi, at the moment we are using the cpu_utilization/target_utilization attribute (in app.yaml) for autoscaling in the app engine flexible environment, however it would be great if we can have the way to mention the memory_utilization metrics as well to decide on the auto scaling. It will give us more control of the auto scaling the instances than now.
ac...@trauzzi.me
Hi, I do not see any memory metrics in neither console nor stackdriver. Is this connected to this issue?
ch...@google.com
Hello Google team, I was directed to this issue by the support team when we raised concerns around the non availability of memory metrics for Auto Scaling. Is this feature 'released' or in roadmap or not considered ? Please provide some details around this
Description
Problem you have encountered: GCP requires vendor specific open telemetry exporter libraries
What you expected to happen: GCP should be able to accept standard OTLP trace data without requiring a GCP specific exporter package to be added to applications.
Steps to reproduce: Integrate with standard open telemetry libraries and export using the standard OTLP wire format.
Other information (workarounds you have tried, documentation consulted, etc): The whole idea behind open telemetry is that people should be able to standardize around a single wire protocol and not have to mess around with vendor specific libraries. Especially when they might not always have access to the source code of the applications they are deploying!
See this blog post for an example:https://thenewstack.io/opentelemetry-otel-is-key-to-avoiding-vendor-lock-in/
I should be able to configure a well known endpoint for any standard OTLP exporter to send data to. Not be forced into adding a Google specific package to my projects. Or in the case of .NET, not even be able to use open telemetry because GCP hasn't put any effort into supporting it yet.
The current architecture of how GCP receives telemetry data is poorly designed.