Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
GCP does include this version image, The problem is that I can build this image but not monitor it. Currently if I want to use a monitored LTS release of Ubuntu I need to use a two year old build.
Chris
Chris
ga...@gmail.com <ga...@gmail.com> #3
Business-critical need to upgrade my micro VM before moving to production env., on GCP's 'Increase Perf.' recommendation. The need for detailed monitoring is severe at the moment, and I've already do-release-upgrade'd my Ubuntu to bionic.
ma...@gmail.com <ma...@gmail.com> #4
Customer would like to have Stackdriver support for Ubuntu 18.04 LTS.
GCP does include this Ubuntu version image, but users cannot monitor it with Stackdriver.
GCP does include this Ubuntu version image, but users cannot monitor it with Stackdriver.
[Deleted User] <[Deleted User]> #5
The workaround for us was to use DataDog. The integration with GCP is impressive and the functionality is excellent, not sure we'll go back to Stackdriver.
xa...@gmail.com <xa...@gmail.com> #6
Is there an estimate on when this will be implemented?
hl...@gmail.com <hl...@gmail.com> #7
Come on, we need stackdriver on Ubuntu 18.04 LTS please!
sl...@r2media.com <sl...@r2media.com> #8
Any update here?
[Deleted User] <[Deleted User]> #9
It's a P3, don't expect a fix any time soon. I initially reported this problem and have since pretty much given up on StackDriver support for 18.04. There are other tools that do the job better.
ra...@orkester.fr <ra...@orkester.fr> #10
Yes, we do need stackdriver for Ubuntu 18.04...
iz...@gmail.com <iz...@gmail.com> #11
i would like to try stackdriver, but i already updated my machines to 18.04
[Deleted User] <[Deleted User]> #12
We have had to use Ubuntu 16.04 for our new deployments until an updated agent is released as we are already heavily invested in Stackdriver. This is rather frustrating that our new deployments are restricted by Stackdriver.
se...@indigitall.nubalia.com <se...@indigitall.nubalia.com> #13
We are interested in the service but if it doesn't support Ubuntu 18 , we will have to find another solution.
ga...@gmail.com <ga...@gmail.com> #14
"GCP does include this Ubuntu version image, but users cannot monitor it with Stackdriver."
This is the thuggest thing I've seen from Google in a long time - considering the footage Stackdriver gets in the GCP console Navigation menu.
This is the thuggest thing I've seen from Google in a long time - considering the footage Stackdriver gets in the GCP console Navigation menu.
rt...@virttrade.com <rt...@virttrade.com> #15
I understand that if the Priority is P2, there is a workaround. What is this workaround?
ro...@gmail.com <ro...@gmail.com> #16
I'd like to add to this request that Google release StackDriver support for Ubuntu 18.04 LTS. (Shouldn't you guys be aware of LTS releases and have a StackDriver deb ready for when they're released to the public?)
[Deleted User] <[Deleted User]> #17
We really need this too and now we're looking for alternatives.
ch...@avondalepark.com <ch...@avondalepark.com> #18
DataDog has worked out really well for us. Having raised this ticket originally, I really don't think I'd go back to StackDriver now.
[Deleted User] <[Deleted User]> #19
Still without a ETA?
pi...@codilime.com <pi...@codilime.com> #20
+1
Anything is going to happen here?
Anything is going to happen here?
[Deleted User] <[Deleted User]> #21
Reason to dump stackdriver...
sh...@gmail.com <sh...@gmail.com> #22
+1
[Deleted User] <[Deleted User]> #23
+1
k....@amutus.co.jp <k....@amutus.co.jp> #24
+1
da...@tualba.it <da...@tualba.it> #25
+1
hh...@emailmeter.com <hh...@emailmeter.com> #26
+1
sh...@eyona.co <sh...@eyona.co> #27
+1
in...@truedata.company <in...@truedata.company> #28
+1
in...@truedata.company <in...@truedata.company> #29
+1
to...@karos.fr <to...@karos.fr> #30
+1
ki...@gmail.com <ki...@gmail.com> #31
+1
ma...@tix.com.au <ma...@tix.com.au> #32
+1
[Deleted User] <[Deleted User]> #33
+1
ar...@cloudtopia.xyz <ar...@cloudtopia.xyz> #34
+1
th...@gmail.com <th...@gmail.com> #35
+1
pl...@plugaai.com <pl...@plugaai.com> #36
+1
ov...@taktik.com <ov...@taktik.com> #37
🙄
mo...@gmail.com <mo...@gmail.com> #38
+1
ri...@mindvalley.com <ri...@mindvalley.com> #39
+1
ce...@gmail.com <ce...@gmail.com> #40
+1
sa...@egym.com <sa...@egym.com> #41
+1
jo...@eluv.io <jo...@eluv.io> #42
+1
da...@gmail.com <da...@gmail.com> #43
+1... WTH, this is a stupid situation. Wow.
ad...@gmail.com <ad...@gmail.com> #44
+1
il...@gmail.com <il...@gmail.com> #45
+1
lu...@gmail.com <lu...@gmail.com> #46
+1
an...@gmail.com <an...@gmail.com> #47
+1
[Deleted User] <[Deleted User]> #48
+1
[Deleted User] <[Deleted User]> #49
+1
[Deleted User] <[Deleted User]> #50
+1
Ti...@gtempaccount.com <Ti...@gtempaccount.com> #51
+1
se...@comhem.com <se...@comhem.com> #52
+1
pi...@codilime.com <pi...@codilime.com> #53
I've packed it to docker container and it works flawlessly on Ubuntu 18.04 (also in kubernetes). That was based on https://hub.docker.com/r/wikiwi/stackdriver-agent/ initially, but I wanted something totally simple what would just work in my case, so it's here: https://github.com/poeyashi/stackdriver-agent .
sj...@gmail.com <sj...@gmail.com> #54
+1
mi...@threedev.com <mi...@threedev.com> #55
+1
lo...@gmail.com <lo...@gmail.com> #56
+1
[Deleted User] <[Deleted User]> #57
Ubuntu 18.04 is the only linux image with ShieldVM features that's not a container-optimized image. It's very disappointing to find out that we can't use it with Stackdriver. Since there isn't any indication that this will be resolved before Ubuntu 20.04 LTS is out we will have to go to the competition for our monitoring needs.
ng...@columbia.edu <ng...@columbia.edu> #58
Why is the only blocker for this issue private? Is this ever going to be worked on?
[Deleted User] <[Deleted User]> #59
+1, unbelievable situation
ra...@gmail.com <ra...@gmail.com> #60
+1
[Deleted User] <[Deleted User]> #61
+1
lb...@ignitenet.com <lb...@ignitenet.com> #62
+1
ma...@gmail.com <ma...@gmail.com> #63
+1
di...@gmail.com <di...@gmail.com> #64
There is already the first point release for Ubuntu 18.04 LTS (18.04.1) and still no support for Stackdriver monitoring :(
[Deleted User] <[Deleted User]> #65
+1
[Deleted User] <[Deleted User]> #66
+1
sc...@gmail.com <sc...@gmail.com> #67
I'd like this feature too please.
[Deleted User] <[Deleted User]> #68
+1
ff...@mxd.cz <ff...@mxd.cz> #69
+11111
[Deleted User] <[Deleted User]> #70
+1
[Deleted User] <[Deleted User]> #71
+1 The weird thing is Ubutu 18.04 LTS image is offered by GCP in GCE instance creation!
ma...@gmail.com <ma...@gmail.com> #72
+1 At least direct us to a tutorial on how to build monitoring agent from source so that we can set it up ourselves. P2 issues are supposed to have workarounds right? Your workaround is to use a different monitoring service?
[Deleted User] <[Deleted User]> #73
(WRONG:) Ubuntu 18.04 LTS is now listed as supported OS for the Stackdriver logging client.
(WRONG:)https://cloud.google.com/logging/docs/agent/
(WRONG:)I have not tried it yet.
This was wrong. There is a difference between Monitoring agent and Logging agent. The Monitoring agent is still not supported on Ubuntu 18.04 LTS.
(WRONG:)
(WRONG:)I have not tried it yet.
This was wrong. There is a difference between Monitoring agent and Logging agent. The Monitoring agent is still not supported on Ubuntu 18.04 LTS.
[Deleted User] <[Deleted User]> #74
I can confirm that Stackdriver Logging agent does indeed support Ubuntu 18.04 LTS but the Monitoring agent is still not supported.
STACKDRIVER MONITORING AGENT
-----------------------------------------------------
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: Starting installation of stackdriver-agent
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: Installing agent for Debian or Ubuntu.
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: Warning: apt-key output should not be parsed (stdout is not a terminal)
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: OK
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: E: The repository 'http://packages.cloud.google.com/apt google-cloud-monitoring-bionic Release' does not have a Release file.
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Could not update apt repositories.
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Please check your network connectivity and
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: make sure you are running a supported Ubuntu/Debian distribution.
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Seehttps://cloud.google.com/monitoring/agent/#supported_operating_systems for a list of supported platforms.
STACKDRIVER LOGGING AGENT
-----------------------------------------------
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Installing StackDriver logging.
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Starting installation of google-fluentd
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Installing agents for Debian or Ubuntu.
Nov 30 13:35:30 ubuntu-1804 startup-script: INFO startup-script-url: Warning: apt-key output should not be parsed (stdout is not a terminal)
Nov 30 13:35:30 ubuntu-1804 startup-script: INFO startup-script-url: OK
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: Selecting previously unselected package google-fluentd.
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: (Reading database ... #015(Reading database ... 5%#015(Reading database ... 10%#015(Reading database ... 15%#015(Reading database ... 20%#015(Reading database ... 25%#015(Reading database ... 30%#015(Reading database ... 35%#015(Reading database ... 40%#015(Reading database ... 45%#015(Reading database ... 50%#015(Reading database ... 55%#015(Reading database ... 60%#015(Reading database ... 65%#015(Reading database ... 70%#015(Reading database ... 75%#015(Reading database ... 80%#015(Reading database ... 85%#015(Reading database ... 90%#015(Reading database ... 95%#015(Reading database ... 100%#015(Reading database ... 60686 files and directories currently installed.)
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: Preparing to unpack .../google-fluentd_1.6.1-1_amd64.deb ...
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: Unpacking google-fluentd (1.6.1-1) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Selecting previously unselected package google-fluentd-catch-all-config.
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Preparing to unpack .../google-fluentd-catch-all-config_0.7_all.deb ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Unpacking google-fluentd-catch-all-config (0.7) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Setting up google-fluentd (1.6.1-1) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Adding system user `google-fluentd' (UID 112) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Adding new group `google-fluentd' (GID 116) ...
Nov 30 13:36:46 ubuntu-1804 startup-script: INFO startup-script-url: Adding new user `google-fluentd' (UID 112) with group `google-fluentd' ...
Nov 30 13:36:46 ubuntu-1804 startup-script: INFO startup-script-url: Not creating home directory `/home/google-fluentd'.
Nov 30 13:36:46 ubuntu-1804 startup-script: INFO startup-script-url: Installing default conffile /etc/google-fluentd/google-fluentd.conf ...
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: Installation of google-fluentd complete.
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: Logs from this machine should be visible in the log viewer at:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url:https://console.cloud.google.com/logs/viewer?project=my-project&resource=gce_instance/instance_id/354278548907250
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: A test message has been sent to syslog to help verify proper operation.
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: Please consult the documentation for troubleshooting advice:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url:https://cloud.google.com/logging/docs/agent
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: You can monitor the logging agent's logfile at:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: /var/log/google-fluentd/google-fluentd.log
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
STACKDRIVER MONITORING AGENT
-----------------------------------------------------
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: Starting installation of stackdriver-agent
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: Installing agent for Debian or Ubuntu.
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: Warning: apt-key output should not be parsed (stdout is not a terminal)
Nov 30 13:34:41 ubuntu-1804 startup-script: INFO startup-script-url: OK
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: E: The repository '
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Could not update apt repositories.
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Please check your network connectivity and
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: make sure you are running a supported Ubuntu/Debian distribution.
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: See
STACKDRIVER LOGGING AGENT
-----------------------------------------------
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Installing StackDriver logging.
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Starting installation of google-fluentd
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:35:28 ubuntu-1804 startup-script: INFO startup-script-url: Installing agents for Debian or Ubuntu.
Nov 30 13:35:30 ubuntu-1804 startup-script: INFO startup-script-url: Warning: apt-key output should not be parsed (stdout is not a terminal)
Nov 30 13:35:30 ubuntu-1804 startup-script: INFO startup-script-url: OK
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: Selecting previously unselected package google-fluentd.
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: (Reading database ... #015(Reading database ... 5%#015(Reading database ... 10%#015(Reading database ... 15%#015(Reading database ... 20%#015(Reading database ... 25%#015(Reading database ... 30%#015(Reading database ... 35%#015(Reading database ... 40%#015(Reading database ... 45%#015(Reading database ... 50%#015(Reading database ... 55%#015(Reading database ... 60%#015(Reading database ... 65%#015(Reading database ... 70%#015(Reading database ... 75%#015(Reading database ... 80%#015(Reading database ... 85%#015(Reading database ... 90%#015(Reading database ... 95%#015(Reading database ... 100%#015(Reading database ... 60686 files and directories currently installed.)
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: Preparing to unpack .../google-fluentd_1.6.1-1_amd64.deb ...
Nov 30 13:36:03 ubuntu-1804 startup-script: INFO startup-script-url: Unpacking google-fluentd (1.6.1-1) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Selecting previously unselected package google-fluentd-catch-all-config.
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Preparing to unpack .../google-fluentd-catch-all-config_0.7_all.deb ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Unpacking google-fluentd-catch-all-config (0.7) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Setting up google-fluentd (1.6.1-1) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Adding system user `google-fluentd' (UID 112) ...
Nov 30 13:36:45 ubuntu-1804 startup-script: INFO startup-script-url: Adding new group `google-fluentd' (GID 116) ...
Nov 30 13:36:46 ubuntu-1804 startup-script: INFO startup-script-url: Adding new user `google-fluentd' (UID 112) with group `google-fluentd' ...
Nov 30 13:36:46 ubuntu-1804 startup-script: INFO startup-script-url: Not creating home directory `/home/google-fluentd'.
Nov 30 13:36:46 ubuntu-1804 startup-script: INFO startup-script-url: Installing default conffile /etc/google-fluentd/google-fluentd.conf ...
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: Installation of google-fluentd complete.
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: Logs from this machine should be visible in the log viewer at:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: A test message has been sent to syslog to help verify proper operation.
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: Please consult the documentation for troubleshooting advice:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: You can monitor the logging agent's logfile at:
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: /var/log/google-fluentd/google-fluentd.log
Nov 30 13:37:31 ubuntu-1804 startup-script: INFO startup-script-url: ==============================================================================
ma...@tix.com.au <ma...@tix.com.au> #75
+1
[Deleted User] <[Deleted User]> #76
+1
[Deleted User] <[Deleted User]> #77
+1
ma...@gmail.com <ma...@gmail.com> #78
Please add this feature for Ubuntu 18.04 LTS. It is really required.
ja...@coingecko.com <ja...@coingecko.com> #79
Same here, running Ubuntu 18.04 LTS, failed with
E: Unable to locate package stackdriver-agent
E: Unable to locate package stackdriver-agent
wi...@pondokmedia.com <wi...@pondokmedia.com> #80
+1
vo...@kettenbach.biz <vo...@kettenbach.biz> #81
+1
ja...@coingecko.com <ja...@coingecko.com> #82
another road block for me to migrate from AWS to GCP sighs~:
RoadBlock Item:
- AWS RDS equivalent - CloudSQL. Postgres version (GCP supports 9.6.x, postgres latest version 11, AWS supports 10.6 - i am using AWS 10.6)
- AWS DMS equivalent - NONE. There is no seamless Database Migrator for postgres (there is for MySQL). Meaning i have to suffer doing all those manual migration task, moving from servers to servers.
- AWS ElastiCache equivalent - MemoryStore. Redis version (GCP supports redis V3, AWS supports V5 - i am using an app with V4, which is not backward compatible with V3), I know it's easy to spin up a redis on GCE using image, but lets not go there.
- CloudSQL Postgres connection limit (Google has well under < 400 max connections, RDS allows up to thousands)
- Now this, the monitoring tool/agent is not supported on Ubuntu 18.04, my company just updated all Ubuntu instances on AWS to 18.04. So without monitoring tool support, this is a very major roadblock.
PS: My team has engaged Google sales team (we had several meetings), we raised some major issues to them about lack of support of major services (be it version, or customization limit), they sounded very positive about the migration but in fact, they offered us some consultation services which will cost alot, using some hacks and workaround just to cover that Google lacks (mentioned in above points). IMO, all they care is about Sales and profit, not really solving customers' issue. If you really want to compete with AWS, what you have to do is offer great tools for seamless migrations, but not forwarding customers who want to migrate to a "workaround" consulting service.
RoadBlock Item:
- AWS RDS equivalent - CloudSQL. Postgres version (GCP supports 9.6.x, postgres latest version 11, AWS supports 10.6 - i am using AWS 10.6)
- AWS DMS equivalent - NONE. There is no seamless Database Migrator for postgres (there is for MySQL). Meaning i have to suffer doing all those manual migration task, moving from servers to servers.
- AWS ElastiCache equivalent - MemoryStore. Redis version (GCP supports redis V3, AWS supports V5 - i am using an app with V4, which is not backward compatible with V3), I know it's easy to spin up a redis on GCE using image, but lets not go there.
- CloudSQL Postgres connection limit (Google has well under < 400 max connections, RDS allows up to thousands)
- Now this, the monitoring tool/agent is not supported on Ubuntu 18.04, my company just updated all Ubuntu instances on AWS to 18.04. So without monitoring tool support, this is a very major roadblock.
PS: My team has engaged Google sales team (we had several meetings), we raised some major issues to them about lack of support of major services (be it version, or customization limit), they sounded very positive about the migration but in fact, they offered us some consultation services which will cost alot, using some hacks and workaround just to cover that Google lacks (mentioned in above points). IMO, all they care is about Sales and profit, not really solving customers' issue. If you really want to compete with AWS, what you have to do is offer great tools for seamless migrations, but not forwarding customers who want to migrate to a "workaround" consulting service.
sa...@gtempaccount.com <sa...@gtempaccount.com> #83
+1
te...@gtempaccount.com <te...@gtempaccount.com> #84
+1
vo...@kettenbach.biz <vo...@kettenbach.biz> #85
I have just found out that it is possible to use the stackdriver-agent from the unstable repository under Ubuntu 18.04:
To do this, simply edit "/etc/apt/sources.list.d/google-cloud-monitoring.list"
and change the line from
"debhttp://packages.cloud.google.com/apt google-cloud-monitoring-bionic main"
in
"debhttp://packages.cloud.google.com/apt google-cloud-monitoring-bionic-artable main"
and then update the package cache with "apt-update".
I could then install the agent with "apt install stackdriver-agent" and start it successfully with "/etc/init.d/stackdriver-agent restart".
I haven't tested the whole thing yet, but the agent starts and data is transferred to Stackdriver Monitoring.
Greetings
VK
To do this, simply edit "/etc/apt/sources.list.d/google-cloud-monitoring.list"
and change the line from
"deb
in
"deb
and then update the package cache with "apt-update".
I could then install the agent with "apt install stackdriver-agent" and start it successfully with "/etc/init.d/stackdriver-agent restart".
I haven't tested the whole thing yet, but the agent starts and data is transferred to Stackdriver Monitoring.
Greetings
VK
ka...@gmail.com <ka...@gmail.com> #86
I believe you ment "deb http://packages.cloud.google.com/apt google-cloud-monitoring-bionic-unstable main"
below example output:
root@dev-15-hz9b:~# cat /etc/apt/sources.list.d/google-cloud-monitoring.list
#debhttp://packages.cloud.google.com/apt google-cloud-monitoring-bionic main
# unstable
debhttp://packages.cloud.google.com/apt google-cloud-monitoring-bionic-unstable main
root@dev-15-hz9b:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@dev-15-hz9b:~# apt search stackdriver
Sorting... Done
Full Text Search... Done
stackdriver-agent/google-cloud-monitoring-bionic-unstable 5.5.2-383.bionic amd64
Stackdriver system metrics collection daemon
root@dev-15-hz9b:~# apt-cache policy stackdriver-agent
stackdriver-agent:
Installed: (none)
Candidate: 5.5.2-383.bionic
Version table:
5.5.2-383.bionic 500
500http://packages.cloud.google.com/apt google-cloud-monitoring-bionic-unstable/main amd64 Packages
root@dev-15-hz9b:~#
below example output:
root@dev-15-hz9b:~# cat /etc/apt/sources.list.d/google-cloud-monitoring.list
#deb
# unstable
deb
root@dev-15-hz9b:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@dev-15-hz9b:~# apt search stackdriver
Sorting... Done
Full Text Search... Done
stackdriver-agent/google-cloud-monitoring-bionic-unstable 5.5.2-383.bionic amd64
Stackdriver system metrics collection daemon
root@dev-15-hz9b:~# apt-cache policy stackdriver-agent
stackdriver-agent:
Installed: (none)
Candidate: 5.5.2-383.bionic
Version table:
5.5.2-383.bionic 500
500
root@dev-15-hz9b:~#
vo...@kettenbach.biz <vo...@kettenbach.biz> #87
Ups, yes, I mean "unstable" for sure
[Deleted User] <[Deleted User]> #88
Thanks for a new year present, VK :) I noticed that Bionic had appeared in the list of supported Ubuntu versions on the documentation page, but could not figure out how to install the agent. Installing it from the unstable repo seems to have worked fine, and I can see the metrics being published.
Here's an installation one-liner, which simplifies the above steps:
curl -sS -o -https://dl.google.com/cloudagents/install-monitoring-agent.sh | sudo REPO_SUFFIX=unstable bash -
There still seem to be some quirks though. For example, when I monitor VM disk utilization, I can filter by instance name, but it is displayed as "${metadata.system_labels\.name}" on the chart. So I guess the whole thing is indeed still a beta on bionic and should not be considered production grade.
Here's an installation one-liner, which simplifies the above steps:
curl -sS -o -
There still seem to be some quirks though. For example, when I monitor VM disk utilization, I can filter by instance name, but it is displayed as "${metadata.system_labels\.name}" on the chart. So I guess the whole thing is indeed still a beta on bionic and should not be considered production grade.
vo...@kettenbach.biz <vo...@kettenbach.biz> #89
Your welcome!
As far as I see, the monitoring-agent is only a re-packaged/re-named collectd using the module write_gcm (has been renamed to write-srackdriver in the offiical source of collectd:https://github.com/collectd/collectd/blob/master/src/write_stackdriver.c )
I'm running collectd on most of our on-premise machines, gathering the data in carbon/whisper. It's a pretty straight forward tool.
I should be possible to debug your issue. Where exactly do you try to filter by instance name?
As far as I see, the monitoring-agent is only a re-packaged/re-named collectd using the module write_gcm (has been renamed to write-srackdriver in the offiical source of collectd:
I'm running collectd on most of our on-premise machines, gathering the data in carbon/whisper. It's a pretty straight forward tool.
I should be possible to debug your issue. Where exactly do you try to filter by instance name?
[Deleted User] <[Deleted User]> #90
It happens when I go into Google Cloud Console (actually StackDriver console) and then into Resource Explorer to create a new chart.
vo...@kettenbach.biz <vo...@kettenbach.biz> #91
I have checked this with me: all instance IDs and names are displayed correctly. Also from the VM running the unstable agent!
Must be something specific to your VM. Me is a Debian 9 Image.
Must be something specific to your VM. Me is a Debian 9 Image.
[Deleted User] <[Deleted User]> #92
Hm.
There must be some difference between Xenial and Bionic versions. I cannot see much difference in syslog journal for stackdriver-agent.
The charts in staskdriver monitoring look different even with identical set-up.
But the alerting policy reports instance name correctly (which is a good thing!).
The "dodgy" VM with an "unstable" version of stackdriver-agent:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# dpkg -s stackdriver-agent
Package: stackdriver-agent
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 3107
Maintainer: Stackdriver Agents <stackdriver-agents@google.com>
Architecture: amd64
Version: 5.5.2-383.bionic
<..>
The fully working one is:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
$ dpkg -s stackdriver-agent
Package: stackdriver-agent
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 5628
Maintainer: Stackdriver Agents <stackdriver-agents@google.com>
Architecture: amd64
Version: 5.5.2-382.xenial
<...>
There must be some difference between Xenial and Bionic versions. I cannot see much difference in syslog journal for stackdriver-agent.
The charts in staskdriver monitoring look different even with identical set-up.
But the alerting policy reports instance name correctly (which is a good thing!).
The "dodgy" VM with an "unstable" version of stackdriver-agent:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
# dpkg -s stackdriver-agent
Package: stackdriver-agent
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 3107
Maintainer: Stackdriver Agents <stackdriver-agents@google.com>
Architecture: amd64
Version: 5.5.2-383.bionic
<..>
The fully working one is:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
$ dpkg -s stackdriver-agent
Package: stackdriver-agent
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 5628
Maintainer: Stackdriver Agents <stackdriver-agents@google.com>
Architecture: amd64
Version: 5.5.2-382.xenial
<...>
[Deleted User] <[Deleted User]> #93
+1
au...@myli.io <au...@myli.io> #94
+1
jf...@gmail.com <jf...@gmail.com> #95
+1
jd...@jdqi.com <jd...@jdqi.com> #96
+1
[Deleted User] <[Deleted User]> #97
+1
hi...@gmail.com <hi...@gmail.com> #98
+1
[Deleted User] <[Deleted User]> #99
+1
ej...@gmail.com <ej...@gmail.com> #100
+1
ig...@google.com <ig...@google.com> #101
As of version 5.5.2-384, the stackdriver-agent package is available in the Bionic stable repo.
Description
GCP does include this Ubuntu version image, but users cannot monitor it with Stackdriver.