By using AWS re:Post, you agree to the Terms of Use

GG logs are pushed intermittently to cloudwatch

0

Hello,

We are using GreenGrass v2 and would like to have logs pushed as frequently as possible. We understand the limitation for certain components (eg telemetry) but our application logs should be sent as near real time as we can. Currently, regardless of the configurations set our logs are only sent intermittently to CloudWatch. Logs are seen every few hours or even few days.

Could anyone please help us understand whats happening?

We are using the following configuration:

      'aws.greengrass.Nucleus': {
        componentVersion: '2.4.0',
        configurationUpdate: {
          merge: `{
            "logging" : {
              "level" : "DEBUG",
              "format" : "JSON"
            }
          }`,
        },
      },
      'aws.greengrass.LogManager': {
        componentVersion: '2.2.1',
        configurationUpdate: {
          merge: `{
            "logsUploaderConfiguration": {
              "systemLogsConfiguration": {
                "uploadToCloudWatch": "true",
                "minimumLogLevel": "DEBUG",
                "diskSpaceLimit": "2",
                "diskSpaceLimitUnit": "KB",
                "deleteLogFileAfterCloudUpload": "true"
              },
              "componentLogsConfigurationMap": {
                "com.component1": {
                  "minimumLogLevel": "DEBUG",
                  "diskSpaceLimit": "2",
                  "logFileDirectoryPath": "/greengrass/v2/logs/",
                  "logFileRegex": "com.component1\\\\w*.log",
                  "diskSpaceLimitUnit": "KB",
                  "deleteLogFileAfterCloudUpload": "true"
                },
                "com.component2": {
                    "minimumLogLevel": "DEBUG",
                    "diskSpaceLimit": "2",
                    "logFileDirectoryPath": "/greengrass/v2/logs/",
                    "logFileRegex": "com.component2\\\\w*.log",
                    "diskSpaceLimitUnit": "KB",
                    "deleteLogFileAfterCloudUpload": "true"
                },
                "aws.greengrass.SageMakerEdgeManager": {
                  "minimumLogLevel": "DEBUG",
                  "logFileDirectoryPath": "/greengrass/v2/logs/",
                  "logFileRegex": "aws.greengrass.SageMakerEdgeManager\\\\w*.log",
                  "diskSpaceLimit": "2",
                  "diskSpaceLimitUnit": "KB",
                  "deleteLogFileAfterCloudUpload": "true"
                },
                "aws.greengrass.SecureTunneling": {
                  "minimumLogLevel": "DEBUG",
                  "logFileDirectoryPath": "/greengrass/v2/logs/",
                  "logFileRegex": "aws.greengrass.SecureTunneling\\\\w*.log",
                  "diskSpaceLimit": "2",
                  "diskSpaceLimitUnit": "KB",
                  "deleteLogFileAfterCloudUpload": "true"
                }
              }
            },
            "periodicUploadIntervalSec": "10"
          }`,
        },
      },
3 Answers
0

Hi, there. I'm sorry for the inconvenience. We are aware of this requirement and have had this feature in our roadmap. But, unfortunately, it's not current supported by LogManager.

You can find details about this issue here under "Log delays" section.

answered 6 months ago
  • Thank you for your answers, but the documentation states that 'The log manager component also uploads new logs periodically. By default, the log manager component uploads new logs every 5 minutes. ' - which is not happening for us as we only see logs are many hours or days. Could you please let us know what can we revise so that the logs are updated every 5min ?

  • Oh, hours or days sounds not right. Is there any log loss? Also, if you could provide logs, it'll help us investigate this issue better.

0

Hi @lihao

How do we check for logs loss? What logs can we provide you that would you help you investigate the issue'?

answered 5 months ago
0

Our problem was solved by changing our configuration file.

answered 5 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions