No Resource information tied with traces?

[census-ecosystem]

No Resource information tied with traces?

[someone1]

And of course I figure out it was an issue on my end as soon as I post the issue... Middleware was wrong by using the passed in Handler vs the ochttp one...

Should be:

        fn := func(w http.ResponseWriter, r *http.Request) {
		traceHandler.ServeHTTP(w, r)
	}

However, I'm still not sure how to link things like Service/Version to the traces, are there special labels we can use? Is there a master list of all special labels for the Stackdriver platform and/or to AppEngine specifically somewhere?

[gottwald]

I guess PR #2 would solve this issue for you, wouldn't it?

[someone1]

Looks like a useful feature but it's not relevant to the issue I've described here. I am able to figure out some labels that the StackDriver platform uses but it still doesn't seem to work correctly (I pulled these from older trace libraries I found for NodeJS/Python/etc.):

attrs = append(attrs, trace.StringAttribute("g.co/gae/app/version", os.Getenv("GAE_VERSION")))
attrs = append(attrs, trace.StringAttribute("gae/instance_id", os.Getenv("GAE_INSTANCE")))
attrs = append(attrs, trace.StringAttribute("g.co/gae/app/module", os.Getenv("GAE_SERVICE")))
attrs = append(attrs, trace.StringAttribute("g.co/gae/app/module_version", os.Getenv("GAE_VERSION")))

These seem to label themselves correctly in the dashboard but when I filter on say Version from the dropdown, no traces show up, even though the Version seems to be tagged appropriately?

I can Filter on Service:

But not on Version:

[gottwald]

gotcha. Sadly I don't know the fields either. Maybe this is something that's faster solved by asking Google support.

[rakyll]

/cc @Ramonza

[gottwald]

Wanted to have that for us as well so I opened a Google Support ticket yesterday and asked (Case 15951800). Once I have a positive response I'll share it here.

[gottwald]

@someone1 They converted my support ticket to a "official" public feature request. You can star this issue to get updates on the implementation progress: https://issuetracker.google.com/issues/109733852
As always there's no ETA given for this FR.

[odeke-em]

I think this issue has been solved since, because:
We now have resource detection as per #84

Kindly paging @songy23 @rghetia @bogdandrutu

[nickm4062]

This issue still exists, is there a reason https://github.com/census-ecosystem/opencensus-go-exporter-stackdriver/blob/master/trace_proto.go#L189 is prefixing all attributes with g.co/r/ ?

looking at the traces that do work in GAE standard it seems they are using
g.co/gae/app/module
go.co/gae/app/version
for these