Hi Kevin, Just wanted to let you know that things look good now. I have been modifying my code and checking the event lines each time.
Once again, thank you very much. Regards Dharani On Sun, Oct 12, 2025 at 12:36 AM Tharaneedharan Vilwanathan < [email protected]> wrote: > Hi Kevin, > > Sorry for the late reply. > > Yes, I did enable the flow event lines. For my program, I did see the > event lines for GC related activities. > > Earlier, I had tried with my own code copying parts of code to start > capture, write, etc. But in my try, I didn't get the event lines for my > code. > > After seeing your mail, I tried the exact code in the blog. That seems to > work (I had to tweak some threshold numbers since duration was much less > than 100ms for the requests). I will try to change my code based on what I > see and continue my experiment. > > Thank you very much. > > Regards > Dharani > > On Thu, Oct 9, 2025 at 8:11 PM Kevin Chowski <[email protected]> wrote: > >> Just to make sure: you've enabled the flow event lines on the webpage, >> right? In the post there is a picture of how to do so right after this >> sentence (at least on mobile): >> >> "Enabling the visualization of all flow events often provides clues that >> hint at the source of a problem." >> >> If that isn't the problem: have you tried running the self-contained >> example provided in the post? If you've enabled this visualization for a >> trace gathered on your own code and it's still not working, try using the >> code given and visualizing that trace. Surely THAT code should work for >> producing the arrows, otherwise there's some error in that post. >> >> >> >> On Wednesday, October 8, 2025 at 1:03:32 AM UTC-7 Tharaneedharan >> Vilwanathan wrote: >> >>> Hi All, >>> >>> I have a quick question. I am going through the flight recorder blog >>> post (https://go.dev/blog/flight-recorder) and trying various things. >>> In particular, I am trying "flow events" to see if I can get the connecting >>> lines with arrow marks. No matter what I do, I couldn't get the connecting >>> lines for my code. What causes those lines? New goroutine? Channel >>> communication? Function call? Calling a function in another package? To the >>> extent I checked, it looks like spawning a new go routine produces >>> connecting lines but I am unable to make it happen for my code. >>> >>> Any clues? Can you please share your thoughts? >>> >>> Regards >>> Dharani >>> >>> >>> >>> >>> -- >> 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 [email protected]. >> To view this discussion visit >> https://groups.google.com/d/msgid/golang-nuts/79f2c324-4f88-40f8-873c-2ae940d68f64n%40googlegroups.com >> <https://groups.google.com/d/msgid/golang-nuts/79f2c324-4f88-40f8-873c-2ae940d68f64n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/CAN-HoCnhjYKZTuydyfkY%2BGv-%3DDqLgGKUDCb9dQNinGaK5UxYiw%40mail.gmail.com.
