Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
Didn't work either... With either mvm enabled or not. I can see that the appengine-web.xml gets updated inside the container, but nothing changes apparently On Thursday, 11 June 2015 17:52:22 UTC+1, Ludovic Champenois wrote: On 6/11/15 8:24 AM, 'Les Vogel' via Google App Engine wrote: One last try, you had it in your email, /home/vmagent/appengine- java-vmruntime/webapps/root/WEB-INF/logging.properties property name=java.util.logging.config.file value= /home/vmagent/appengine-java-vmruntime/webapps/root/ WEB-INF/logging.properties/ If the full path doesn't work, I don't know what else to suggest to you. Maybe file a bug... Maybe MVM is not setting the defaut current directory to the root of the app? Ludo On Thu, Jun 11, 2015 at 12:38 AM, Paolo Rascuna paolo@imagini.net javascript: wrote: I'm afraid, that didn't help. On Wednesday, 10 June 2015 18:51:28 UTC+1, Les Vogel wrote: Try changing it to /app/WEB-INF/logging.properties Les On Wed, Jun 10, 2015 at 2:26 AM, Paolo Rascuna paolo@imagini.net wrote: Thanks Les, but I already have such lines in my logging.properties and these lines in my appengine-web.xml !-- Configure java.util.logging -- system-properties property name=java.util.logging.config.file value=WEB-INF/logging.properties/ /system-properties At this point I'm afraid the the logging.properties is not being read (even though, logging into the docker container (docker exec -ti `docker ps -q` bash ) I can see the file in /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF On Thursday, 4 June 2015 17:48:58 UTC+1, Les Vogel wrote: Not that I'm aware of, but the source code can be found at https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/ It's just the messages I didn't want to see in my debug logs. On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform Support) pay...@google.com wrote: Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
I'm afraid, that didn't help. On Wednesday, 10 June 2015 18:51:28 UTC+1, Les Vogel wrote: Try changing it to /app/WEB-INF/logging.properties Les On Wed, Jun 10, 2015 at 2:26 AM, Paolo Rascuna paolo@imagini.net javascript: wrote: Thanks Les, but I already have such lines in my logging.properties and these lines in my appengine-web.xml !-- Configure java.util.logging -- system-properties property name=java.util.logging.config.file value=WEB-INF/logging.properties/ /system-properties At this point I'm afraid the the logging.properties is not being read (even though, logging into the docker container (docker exec -ti `docker ps -q` bash ) I can see the file in /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF On Thursday, 4 June 2015 17:48:58 UTC+1, Les Vogel wrote: Not that I'm aware of, but the source code can be found at https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/ It's just the messages I didn't want to see in my debug logs. On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform Support) pay...@google.com wrote: Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine . To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | le...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
On 6/11/15 8:24 AM, 'Les Vogel' via Google App Engine wrote: One last try, you had it in your email, /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF/logging.properties property name=java.util.logging.config.file value=/home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF/logging.properties/ If the full path doesn't work, I don't know what else to suggest to you. Maybe file a bug... Maybe MVM is not setting the defaut current directory to the root of the app? Ludo On Thu, Jun 11, 2015 at 12:38 AM, Paolo Rascuna paolo.rasc...@imagini.net mailto:paolo.rasc...@imagini.net wrote: I'm afraid, that didn't help. On Wednesday, 10 June 2015 18:51:28 UTC+1, Les Vogel wrote: Try changing it to /app/WEB-INF/logging.properties Les On Wed, Jun 10, 2015 at 2:26 AM, Paolo Rascuna paolo@imagini.net wrote: Thanks Les, but I already have such lines in my logging.properties and these lines in my appengine-web.xml !-- Configure java.util.logging -- system-properties property name=java.util.logging.config.file value=WEB-INF/logging.properties/ /system-properties At this point I'm afraid the the logging.properties is not being read (even though, logging into the docker container (docker exec -ti `docker ps -q` bash ) I can see the file in /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF On Thursday, 4 June 2015 17:48:58 UTC+1, Les Vogel wrote: Not that I'm aware of, but the source code can be found at https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/ It's just the messages I didn't want to see in my debug logs. On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform Support) pay...@google.com wrote: Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to:
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
One last try, you had it in your email, /home/vmagent/appengine- java-vmruntime/webapps/root/WEB-INF/logging.properties property name=java.util.logging.config.file value= /home/vmagent/appengine-java-vmruntime/webapps/root/ WEB-INF/logging.properties/ If the full path doesn't work, I don't know what else to suggest to you. On Thu, Jun 11, 2015 at 12:38 AM, Paolo Rascuna paolo.rasc...@imagini.net wrote: I'm afraid, that didn't help. On Wednesday, 10 June 2015 18:51:28 UTC+1, Les Vogel wrote: Try changing it to /app/WEB-INF/logging.properties Les On Wed, Jun 10, 2015 at 2:26 AM, Paolo Rascuna paolo@imagini.net wrote: Thanks Les, but I already have such lines in my logging.properties and these lines in my appengine-web.xml !-- Configure java.util.logging -- system-properties property name=java.util.logging.config.file value=WEB-INF/logging.properties/ /system-properties At this point I'm afraid the the logging.properties is not being read (even though, logging into the docker container (docker exec -ti `docker ps -q` bash ) I can see the file in /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF On Thursday, 4 June 2015 17:48:58 UTC+1, Les Vogel wrote: Not that I'm aware of, but the source code can be found at https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/ It's just the messages I didn't want to see in my debug logs. On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform Support) pay...@google.com wrote: Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations |
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
Thanks Les, but I already have such lines in my logging.properties and these lines in my appengine-web.xml !-- Configure java.util.logging -- system-properties property name=java.util.logging.config.file value=WEB-INF/logging.properties/ /system-properties At this point I'm afraid the the logging.properties is not being read (even though, logging into the docker container (docker exec -ti `docker ps -q` bash ) I can see the file in /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF On Thursday, 4 June 2015 17:48:58 UTC+1, Les Vogel wrote: Not that I'm aware of, but the source code can be found at https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/ It's just the messages I didn't want to see in my debug logs. On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform Support) pay...@google.com javascript: wrote: Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo@imagini.net javascript: wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | le...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com javascript:. To post to this group, send email to google-a...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
Try changing it to /app/WEB-INF/logging.properties Les On Wed, Jun 10, 2015 at 2:26 AM, Paolo Rascuna paolo.rasc...@imagini.net wrote: Thanks Les, but I already have such lines in my logging.properties and these lines in my appengine-web.xml !-- Configure java.util.logging -- system-properties property name=java.util.logging.config.file value=WEB-INF/logging.properties/ /system-properties At this point I'm afraid the the logging.properties is not being read (even though, logging into the docker container (docker exec -ti `docker ps -q` bash ) I can see the file in /home/vmagent/appengine-java-vmruntime/webapps/root/WEB-INF On Thursday, 4 June 2015 17:48:58 UTC+1, Les Vogel wrote: Not that I'm aware of, but the source code can be found at https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/ It's just the messages I didn't want to see in my debug logs. On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform Support) pay...@google.com wrote: Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | le...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
Not that I'm aware of, but the source code can be found at https://github.com/GoogleCloudPlatform/appengine-java-vm-runtime/ It's just the messages I didn't want to see in my debug logs. On Thu, Jun 4, 2015 at 9:34 AM, Nick (Cloud Platform Support) pay...@google.com wrote: Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo.rasc...@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | le...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | l...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
Hey Les, Some of the lines in that logging.properties example are quite interesting. Are they documented anywhere in relation to Managed VMs? Thanks, Nick On Thursday, June 4, 2015 at 12:05:11 PM UTC-4, Les Vogel wrote: The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo.rasc...@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | le...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | l...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/5577d3b9-e19e-4ec0-92d0-02e04c049327%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
The important thing was setting the classes your interested in logs for in your: *logging.properties* if you don't do that, you won't see anything. From one of mine: # Set the default logging level for all loggers to INFO *.level = INFO* # Loggers *com.example.bigtable.managedvms.level=ALL* org.apache.http.level=OFF org.apache.http.wire.level=OFF com.google.apphosting.repackaged.org.apache.http.wire.level=OFF com.google.apphosting.vmruntime.VmAppLogsWriter.level=OFF com.google.apphosting.vmruntime.VmApiProxyDelegate=OFF com.google.apphosting.vmruntime.level=OFF On Thu, Jun 4, 2015 at 2:49 AM, Paolo Rascuna paolo.rasc...@imagini.net wrote: Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com. To post to this group, send email to google-a...@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | le...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | l...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAGB1p5iyyv%2BbX5Ymn2zq5zrQbRMbvLfnfDiC5QiKiYPR0sog1g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
Thank you Les, but that's not working for me... I tried that already, but that's the docker logs output $ docker logs -f `docker ps -q` Info: Limiting Java heap size to: 1456M Running locally and DBG_ENABLE is set, enabling standard Java debugger agent Listening for transport dt_socket at address: 5005 2015-06-04 09:05:08.860:INFO::main: Logging initialized @571ms 2015-06-04 09:05:09.001:INFO::main: Redirecting stderr/stdout to /var/log/app_engine/STDERR.2015_06_04.log//var/log/app_engine/STDOUT.2015_06_04.log On Wednesday, 3 June 2015 18:09:45 UTC+1, Les Vogel wrote: There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo@imagini.net javascript: wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengi...@googlegroups.com javascript:. To post to this group, send email to google-a...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | le...@google.com javascript: | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1e58f4c9-5cc1-4aab-b055-224124f6c976%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Managed VM and logging with gcloud-maven-plugin
Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Managed VM and logging with gcloud-maven-plugin
There are changes coming to improve things in the next few weeks. In the mean time, here's what I do: Make sure .level=INFO or what you need in your logging.properties . For the class(es) I'm working with I set the class logging explicitly to: com.example.bigtable.managedvms.level=ALL Then in a separate window, I run the following script on my Mac: #!/bin/bash docker logs -f `docker ps -q` On Wed, Jun 3, 2015 at 6:39 AM, Paolo Rascuna paolo.rasc...@imagini.net wrote: Hi, I have a java project running on Managed VM, and I use gcloud-maven-plugin to run the app locally, simply mvn gcloud:run I would like to see my application logs straight in the console, but so far I can only see the access logs. The only way that I found is to login directly into the docker container and read the logs from /var/log/app_engine/ but every time I make some code change and I rebuild the docker image, the container I'm logged in of course gets destroyed and I need to log in again... quite a long process so. I also tried to add more parameters, like mvn -Dgcloud.log_level=debug -Dgcloud.enable_mvm_logs -X gcloud:run but still no luck. Do you guys have any suggestion? -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com https://groups.google.com/d/msgid/google-appengine/2b2e4858-9771-4964-acb6-c02704a9a0b3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Les Vogel | Cloud Developer Relations | l...@google.com | 408-676-7023 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CAGB1p5idzk7HwiPpERAHDU3mA5QiSMtDp7qFcCxpefh6Lh_Ssg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
