cool. if the granularity and the info open census provides is sufficient for your use case that’s the right way.
go tool trace is for analyzing interaction between go runtime and the application. On Fri, May 25, 2018 at 1:22 PM Neven Miculinić <neven.miculi...@gmail.com> wrote: > Hey, > > in the end I've used opencensus which has the same features as go's spans, > but it's designed for distributed tracing. I already have multiple backend > support, which supports more advanced filtering options than > chrome://tracings's catapult viewer. > > Thanks, > Neven Miculinić > > > On Tue, 8 May 2018 at 08:42, Tarmigan <tarmigan+gol...@gmail.com> wrote: > >> In addition to the documentation that Hana pointed to, she also just >> gave a great talk that included a walk through of the new features and >> how they may be used to view high latency events: >> https://www.youtube.com/watch?v=FJQjUueBJ2A >> >> It's worth watching if you are interested in tracing and latency, and >> I'm looking forward to trying the new APIs soon. >> >> >> On Mon, May 7, 2018 at 1:31 PM, Hyang-Ah Hana Kim <hyan...@gmail.com> >> wrote: >> > Have you tried the new annotation api in the tip? >> > tip.golang.org/pkg/runtime/trace? >> > Please see if annotating in the source code with Region or Task would >> work >> > for your case. >> > >> > >> > On Wed, May 2, 2018 at 8:59 AM, <neven.miculi...@gmail.com> wrote: >> >> >> >> High level goal: >> >> >> >> I have an application with significant number of goroutine experiencing >> >> latency issues. I want to detect and dissect where those issues arise >> and >> >> determine how can I fix them. For that I’ve use go tool trace >> >> >> >> Middle-level features: >> >> >> >> I want to filter event in the catapult viewer (( I cannot find >> >> documentation how to do it, and JS ecosystem I’m not really proficient >> in )) >> > >> > >> > What kind of filtering do you want to perform? >> >> >> >> Since I’m using errgroups, event names are all >> >> “$(pwd)/vendor/golang.org/x/sync/errgroup.(*Group).Go.func1” Not >> really >> >> informative. I’d like to include/exclude specific stack frame from >> appearing >> >> on the regex level perhaps? e.g. >> >> if I have stack A ->B->C and I’m filtering C, I’m expecting to see >> only B >> >> on the summary, and A->B in the details >> > >> > >> > If you can use the annotation api, you can mark the interesting >> goroutine >> > execution with Region and with the new trace (included in the tip) you >> can >> > select only the goroutines with the specified Region. >> > >> >> >> >> In chrome tracing format specification, it says there are event types. >> I >> >> cannot find how to do filtering on them in the catapult viewer >> > >> > >> > I don't think the catapult viewer supports any kind of filtering based >> on >> > the event type, or I am afraid I misunderstood what you want. >> > >> > >> > -- >> > __ >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "golang-nuts" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to golang-nuts+unsubscr...@googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. >> > -- __ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
