I can't see running instances on my apps

117 views
Skip to first unread message

Abel Alcaraz Domínguez

unread,
Jan 3, 2022, 5:03:14 AM1/3/22
to Google App Engine
Hi,

any idea why I can't see the number of instances started in my apps?

in none of my projects I can see the number of instances started, with this configuration:

runtime: nodejs16
instance_class: F1
service: default
automatic_scaling:
  min_instances: 1
  max_instances: 2
handlers:
# Serve all static files with url ending with a file extension.
- url: /(.*\..+)$
  static_files: build/\1
  upload: build/(.*..+)$
  secure: always
  redirect_http_response_code: 301
# catch all handler to index.html
- url: .*
  static_files: build/index.html
  upload: build/index.html
  secure: always
  redirect_http_response_code: 301

Thanks in advance for your help
Abel

Alejandro L

unread,
Jan 4, 2022, 10:13:45 AM1/4/22
to Google App Engine

Hello Abel,

Thank you for your message.

I have deployed a sample application on my App Engine environment using the configuration that you attach as my app.yaml and I have not been able to reproduce this behavior. I would like to ask, how are you attempting to see the instance list for each deployment? The most accurate and up to date data for this kind of monitoring is to use the command ‘gcloud app instances list’, which is how I can find the min_instance which is running for this sample deployment. Does this work for you?

Alejandro L

Alejandro L

unread,
Jan 5, 2022, 6:22:48 AM1/5/22
to Google App Engine
Hello Abel,

You responded privately to me about this, explaining that you understand that they should be the same. I have checked my dashboard in [1] and I have seen the instance graph update with the minimum instance defined in the YAML file that you provided me with, which is what I expect.

Under my experience, it usually takes a few minutes for the monitoring graphs and lists to update, while the shell always returns the most up to date information. Therefore, if this is checked right after or during deployment, you might not see the most up to date information, but this should not take long. 

However, I would like to point out that sometimes, I have faced that if the application has any misconfiguration, it might be deployed but not start any instance. If this is the case, you will not be able to access it by clicking on 'default' in the services page [2] as the service will return an error. This misconfiguration could arise from the handlers, as they are dependent on the deployment code, which I do not have access to.

Therefore, I would like to suggest you to attempt the deployment documented in this guide [3], however ensuring that you deploy using an app.yaml as documented in [4], and check if you can see the instances then.

[1]:
[2]:
[3]:
[4]:
Reply all
Reply to author
Forward
0 new messages