Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.5.0-b1
-
Component/s: None
-
Labels:None
-
Epic Link:
Description
The Logs model performs the storage of various logs, such as module and gateway logs. However, systems that log data for modules and gateways are unaware that there is a character-length limit, and thus encounter an error in cases where they exceed it. Instead, we should make an effort to automatically split logs to adhere to the character-length limitation.
- Update the Logs model for module and gateway logs to ensure log data that exceeds the datatype character limit is split into multiple log entries
- We often return the ID of the log entry that was created. For backward compatibility, we will continue to do so, but only for the first record created in the set.
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
| Story Points | 5 |
Tyson Phillips (Inactive)
made changes -
| Epic Link |
|
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.5.0 Sprint 4 [ 75 ] |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked higher |
Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Tyson Phillips (Inactive)
made changes -
| Summary | Update data stored by the Logs model to automatically split logs | Automatically split log data stored for gateways and modules |
Tyson Phillips (Inactive)
made changes -
| Description |
The *Logs* model performs the storage of various logs, such as module logs, gateway logs, email logs, cron logs, etc. However, systems that use these logging methods are unaware that there are character-length limitations to the data stored, and thus encounter an error. Instead, we should make an effort to automatically split logs to adhere to the character-length limitation.
# Update the *Logs* model for all stored logs to ensure log data that exceeds the datatype character limitations is split into multiple log entries #* We often return the ID of the log entry that was created. For backward compatibility, we will continue to do so, but only for the first record created in the set. |
The *Logs* model performs the storage of various logs, such as module and gateway logs. However, systems that log data for modules and gateways are unaware that there is a character-length limit, and thus encounter an error in cases where they exceed it. Instead, we should make an effort to automatically split logs to adhere to the character-length limitation.
# Update the *Logs* model for module and gateway logs to ensure log data that exceeds the datatype character limit is split into multiple log entries #* We often return the ID of the log entry that was created. For backward compatibility, we will continue to do so, but only for the first record created in the set. |
Automated transition triggered when Tyson Phillips (Inactive) created pull request #590 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 hour, 34 minutes [ 5640 ] | |
| Worklog Id | 11787 [ 11787 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #590 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
