Is it worth mentioning how to enable logs?

[xynova]

Should the examples show how to turn logs on?

  metadata = {
    gce-container-declaration = module.container_metadata_spec.metadata_value
    google-logging-enabled = "true"
  }

[morgante]

Sure, feel free to add this to an example.

[dts]

This would be great - I am happy to push up a PR if that's helpful, but I don't want to step on anyones toes.

[xynova]

no worries, I forked the project in order to do it and never did, sorry about that

[morgante]

A PR would definitely be appreciated.

[dts]

@morgante - let me know if you had something else in mind r.e. PR #62

[0xjjpa]

Sorry to comment on a closed thread, but albeit the logging seems to be enabled, it seems that unless we enable gcplogs this would effectively only log the machine vitals and not the logs of the actual container.

It seems that there's already some train of thought for enabling this, but I've yet to find an example on how to enable this for a COS image. From my understanding, we need to add something like the following in the COS image under /etc/docker/daemon.json:

{
  "log-driver": "gcplogs",
  "log-opts": {
    "gcp-project": "removed",
    "env": "host"
  }
}

Right now I'm using cos-dev-84-13078-0-0 and I get the following information:

$ cat /etc/docker/daemon.json
{
        "live-restore": true,
        "storage-driver": "overlay2",
        "mtu": 1460
}

In short, even if we add this line (i.e. google-logging-enabled = "true") in our VM metadata definition, the agent has yet to know how to send the container information to GCP. Would that be a correct statement?

[morgante]

Interesting, I haven't dug into this but can reopen the issue if someone wants to investigate further.