You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since OpenTelemetry is widely used in serverless applications, adding instrumentation for GCF would improve usability.
While an aws_lambda instrumenter already exists, there is no equivalent for Google Cloud Functions, which is widely used for serverless deployments. Providing this support would help OpenTelemetry users monitor and trace their workloads in Google Cloud Functions with the same level of insight as AWS Lambda.
Describe the solution you'd like
Create a new instrumenter for Google Cloud Functions. Similar to what's already available in aws_lambda instrumenter
@beijiez can you expand a little on what you would like to see instrumented? Either specifics or some CUJs you have would be helpful
Sure, I was thinking of starting with general stuff like request duration, error rates, and external service call counts. If it can then be sent to a backend such as Jaeger or Google Cloud Monitoring (because GCF) would be great.
What problem do you want to solve?
Since OpenTelemetry is widely used in serverless applications, adding instrumentation for GCF would improve usability.
While an aws_lambda instrumenter already exists, there is no equivalent for Google Cloud Functions, which is widely used for serverless deployments. Providing this support would help OpenTelemetry users monitor and trace their workloads in Google Cloud Functions with the same level of insight as AWS Lambda.
Describe the solution you'd like
Additional Context
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: