Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

LogConfig: Lost time key when edit JSON config #296

Closed
chenhaiyun opened this issue Jun 25, 2024 · 0 comments · Fixed by #300
Closed

LogConfig: Lost time key when edit JSON config #296

chenhaiyun opened this issue Jun 25, 2024 · 0 comments · Fixed by #300
Assignees
@chenhaiyun
Labels
bug Something isn't working

Comments

@chenhaiyun
Copy link
Contributor

Describe the bug

  1. There is an old version JSON config without JSON schema.
  2. Edit this config and parse log
  3. Save config will lost time key

Expected Behavior

Time key reserved when edit old version log config

Current Behavior

time key lost

Reproduction Steps

  1. There is an old version JSON config without JSON schema.
  2. Edit this config and parse log
  3. Save config will lost time key

Possible Solution

No response

Additional Information/Context

No response

Solution Version

v2.2

AWS Region. e.g., us-east-1

No response

Other information

No response
@chenhaiyun chenhaiyun added the bug Something isn't working label Jun 25, 2024
@chenhaiyun chenhaiyun changed the title LogConfig: Missing time key when edit JSON config LogConfig: Lost time key when edit JSON config Jun 25, 2024
@chenhaiyun chenhaiyun self-assigned this Jun 25, 2024
@James96315 James96315 mentioned this issue Jul 22, 2024
Merged
James96315 added a commit that referenced this issue Jul 22, 2024
@James96315
[2.2.1] - 2024-07-22 (#300)
876df63 
### Added

- Optimised instance list performance. #76
- Added support for using Unix epoch time format as the time key for single line text log type.

### Fixed

- Fixed an issue that missing time key when editing JSON config. #296
- Fixed an issue that upgrading to v2.2.0 failed due to missing CMK permissions. #297


---------

Co-authored-by: James Ma <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chenhaiyun chenhaiyun

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[2.2.1] - 2024-07-22 James96315/centralized-logging-with-opensearch
1 participant
@chenhaiyun