App Engine support #8

Activity

1. dmelikyan commented on Nov 16, 2017

   

   dmelikyan

   on Nov 16, 2017

   Member

   More actions

   The agent is now compatible with App Engine, starting v2.2.3. However, the ppof panics in App Engine standard environment. We'll try to find out if profiling is possible at all. In App Engine flexible environment the agent works without any problems.

   The agent can still be used App Engine standard local development environment. Because of the limitations on background tasks and context dependency of http client, the agent should be used in manual profiling and reporting mode (see readme), here is an example:

   package hello
   
   import (
   	"fmt"
   	"net/http"
   
   	"google.golang.org/appengine"
   	"google.golang.org/appengine/urlfetch"
   
   	"github.com/stackimpact/stackimpact-go"
   )
   
   var agent *stackimpact.Agent
   
   func init() {
   	agent = stackimpact.Start(stackimpact.Options{
   		AgentKey: "your agent key",
   		AppName: "AppEngineStandardApp",
   		DisableAutoProfiling: true,
   	})
   
   	http.HandleFunc("/", handler)
   }
   
   func handler(w http.ResponseWriter, r *http.Request) {
   	span := agent.Profile()
   	defer span.Stop()
   
   	ctx := appengine.NewContext(r)
   	client := urlfetch.Client(ctx)
   	defer agent.ReportWithHTTPClient(client)
   
   	fmt.Fprintln(w, "Hello, world!")
   }
   
2. benguild commented on Nov 16, 2017

   

   benguild

   on Nov 16, 2017

   Author

   More actions

   So you're saying that the code above will not work in Standard on a live deployment?
3. dmelikyan commented on Nov 16, 2017

   

   dmelikyan

   on Nov 16, 2017

   Member

   More actions

   It didn't work for me, the pprof panics. I've also tried pprof CPU profiler directly, without the agent, same error.
4. benguild commented on Nov 16, 2017

   

   benguild

   on Nov 16, 2017

   Author

   More actions

   You can't CPU profile on App Engine Standard as far as I know. However, you can use heap profiling and some others.
5. dmelikyan commented on Nov 16, 2017

   

   dmelikyan

   on Nov 16, 2017

   Member

   More actions

   I'll see if any of the profilers works. If yes, then we could add a possibility to disable some profilers and keep only supported ones.
6. benguild commented on Nov 16, 2017

   

   benguild

   on Nov 16, 2017

   Author

   More actions

   Anything that uses syscall is banned, and probably some others. However the heap one definitely works.