Modify Timestamp of phosphor-hostlogger

Modify Timestamp of phosphor-hostlogger

[Spencer Ku (古世瑜)]

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

Hi All,
We have worked on a redfish URI that provides host log information, which is based on obmc-console and phosphor-hostlogger. Now we can get host log and fill information into host log entry, but here we have a problem about timestamp.

One of the log entry level “created time”, need to follow the time format like RFC3339, and for now, the host log only provides hour, minute, and second time info. We want to modify the timestamp to RFC3339 format to fit the log entry time format.

Here is a sample host log with timestamp providing by phosphor-hostlogger:
[ 00:00:31 ] >>> Log collection started at 1970-01-01 00:00:31

After modified, the message will be liked:
[ 1970-01-01T00:00:31+00:00 ] >>> Log collection started at 1970-01-01 00:00:31

if the changes make sense, we will push the changes to upstream.
Please let us know if there's any issue, thank you.

Sincerely,
Spencer

[-- Attachment #2: Type: text/html, Size: 4379 bytes --]

Re: Modify Timestamp of phosphor-hostlogger

[Artem Senichev]

Hi Spencer,

I think it is a good idea.
We didn't have a service to handle these logs, so the short format was
due to the compact display output.

--
Best regards,
Artem Senichev

On Wed, Oct 14, 2020 at 1:36 PM Spencer Ku (古世瑜)
<Spencer.Ku@quantatw.com> wrote:
>
> Hi All,
>
> We have worked on a redfish URI that provides host log information, which is based on obmc-console and phosphor-hostlogger. Now we can get host log and fill information into host log entry, but here we have a problem about timestamp.
>
>
>
> One of the log entry level “created time”, need to follow the time format like RFC3339, and for now, the host log only provides hour, minute, and second time info. We want to modify the timestamp to RFC3339 format to fit the log entry time format.
>
>
>
> Here is a sample host log with timestamp providing by phosphor-hostlogger:
>
> [ 00:00:31 ] >>> Log collection started at 1970-01-01 00:00:31
>
>
>
> After modified, the message will be liked:
>
> [ 1970-01-01T00:00:31+00:00 ] >>> Log collection started at 1970-01-01 00:00:31
>
>
>
> if the changes make sense, we will push the changes to upstream.
>
> Please let us know if there's any issue, thank you.
>
>
>
> Sincerely,
>
> Spencer

RE: Modify Timestamp of phosphor-hostlogger

[Spencer Ku (古世瑜)]

Hi Artem,
Thanks for your reply. I had already pushed the change to gerrit.
Please take a look, thank you.

Sincerely,
Spencer Ku

-----Original Message-----
From: Artem Senichev <artemsen@gmail.com> 
Sent: Thursday, October 15, 2020 2:46 PM
To: Spencer Ku (古世瑜) <Spencer.Ku@quantatw.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Modify Timestamp of phosphor-hostlogger

Hi Spencer,

I think it is a good idea.
We didn't have a service to handle these logs, so the short format was due to the compact display output.

--
Best regards,
Artem Senichev

On Wed, Oct 14, 2020 at 1:36 PM Spencer Ku (古世瑜)
<Spencer.Ku@quantatw.com> wrote:
>
> Hi All,
>
> We have worked on a redfish URI that provides host log information, which is based on obmc-console and phosphor-hostlogger. Now we can get host log and fill information into host log entry, but here we have a problem about timestamp.
>
>
>
> One of the log entry level “created time”, need to follow the time format like RFC3339, and for now, the host log only provides hour, minute, and second time info. We want to modify the timestamp to RFC3339 format to fit the log entry time format.
>
>
>
> Here is a sample host log with timestamp providing by phosphor-hostlogger:
>
> [ 00:00:31 ] >>> Log collection started at 1970-01-01 00:00:31
>
>
>
> After modified, the message will be liked:
>
> [ 1970-01-01T00:00:31+00:00 ] >>> Log collection started at 1970-01-01 
> 00:00:31
>
>
>
> if the changes make sense, we will push the changes to upstream.
>
> Please let us know if there's any issue, thank you.
>
>
>
> Sincerely,
>
> Spencer