google-cloud-trace | 易学教程

How to tracing a request through a chain of microservices end-to-end?

阅读更多关于 How to tracing a request through a chain of microservices end-to-end?

问题 I am using OpenCensus in Go to push tracing data to Stackdriver for calls involving a chain of 2 or more micro services and I noticed that I get many traces which contain spans only for certain services but not the entire end to end call. At the moment I attribute this to the fact that not all calls are traced (only a certain sample) and each service decides whether to trace its current span or not. Is this the way it is intended to work? Is there any way to make sure when a trace is sampled,

How to do a simple Google Cloud Trace request in Java

阅读更多关于 How to do a simple Google Cloud Trace request in Java

问题 I am trying to perform a simple push traces operation to my Google Cloud Trace project and I simply can't seem to send data across. Here is my build.gradle file: apply plugin: 'java' repositories { mavenCentral() } dependencies { compile 'com.google.oauth-client:google-oauth-client-java6:1.20.0' compile 'com.google.apis:google-api-services-cloudtrace:v1-rev6-1.22.0' } jar { from configurations.compile.collect { it.isDirectory() ? it : zipTree(it) } } And the following Java code with dummy

Using google cloud trace API

阅读更多关于 Using google cloud trace API

问题 I am attempting to use the grpc client for the Stackdriver/google cloud trace definition at https://github.com/googleapis/googleapis/blob/master/google/devtools/cloudtrace/v1/trace.proto I am sending the protobuf for the traces { traces { project_id: "brightcove-rna-master" trace_id: "A096D4956A424EEB98AE7863505B1E1F" spans { span_id: 1 kind: RPC_CLIENT name: "/bigtableAapiGrpcstaging_aggregated/queryDataSetInternal/buildScan" start_time { seconds: 1459230665 nanos: 705000000 } end_time {

Google Cloud Trace 192.168.1.1

阅读更多关于 Google Cloud Trace 192.168.1.1

问题 In the Trace page of Google Cloud Console I can see address 192.168.1.1 which takes a lot of time to execute. What is this address? From where? Is it from internal cloud's infrastructure? Or is it mine local address (if it possible)? 回答1: After talk with Google Cloud Support appears that 192.168.1.1 is exactly machine IP address on which Google Cloud Function is launched. But the interesting thing is that this address only appears if console.* things are in the code. So, for example I'm using

Does AppEngine Cloud Trace require AppStats?

阅读更多关于 Does AppEngine Cloud Trace require AppStats?

问题 Google's AppEngine has upgraded their Developer's Console and it includes a monitoring tool called Cloud Trace. Is this an improved version of the AppStats profiling tool? If so, can I remove the configuration files that were previously required, like appengine_config.py and the console path in app.yaml ? builtins: - appstats: on 回答1: Cloud Trace is in beta, meaning "it's not covered by any SLA or deprecation policy and may be subject to backward-incompatible changes", while AppStats is a

Does AppEngine Cloud Trace require AppStats?

阅读更多关于 Does AppEngine Cloud Trace require AppStats?

Google's AppEngine has upgraded their Developer's Console and it includes a monitoring tool called Cloud Trace . Is this an improved version of the AppStats profiling tool? If so, can I remove the configuration files that were previously required, like appengine_config.py and the console path in app.yaml ? builtins: - appstats: on Cloud Trace is in beta, meaning "it's not covered by any SLA or deprecation policy and may be subject to backward-incompatible changes", while AppStats is a supported component of App Engine. The implication, to me, is that you probably should not yet depend on Cloud

How to tracing a request through a chain of microservices end-to-end?

阅读更多关于 How to tracing a request through a chain of microservices end-to-end?

I am using OpenCensus in Go to push tracing data to Stackdriver for calls involving a chain of 2 or more micro services and I noticed that I get many traces which contain spans only for certain services but not the entire end to end call. At the moment I attribute this to the fact that not all calls are traced (only a certain sample) and each service decides whether to trace its current span or not. Is this the way it is intended to work? Is there any way to make sure when a trace is sampled, it is done so by all services in the call chain? Architecturally I will say when you are developing