Develop new RSS functionality #72
Description
The RSS functionality is described in the draft, so we need to implement it.
Details:
android appliaction
rss reader displays the content not properly formatted
The component name is missing
The text block with incident description is short due to timestamp at the same line (maybe line break should be implemented)
Case 1-A) one affected service - first trigger msg
Title:
Structure: [ServicenameShort] status changed to [Status-Severity]
Example: ELB status changed to minor issue
Description:
Structure: A [Status-Severity] was detected at [timestamp] UTC for [Servicename-Long] in [Region].
Example: A minor issue was detected at 2024-01-23 10:45 UTC, for Elastic Load Balancer in EU-DE.
Case 1-B) one affected service - status update msgs
Title:
Structure: Update published for: [Incident-Title]
Example: Update published for: Reduced performance for ECS due to network issue
Description:
Structure: An update was provided at [timestamp] UTC for [Servicename-Long] in [Region]: [Incident-Status] - [Update-Msg]
Example: An update was provided at 2024-01-23 10:45 UTC for Cloud Container Engine in EU-DE: Investigation started - Our experts are checking the situation and we do everything to sort out the situation asap.
Case 2-A) multiple affected services - first trigger msg
Title:
Structure: Status change of multiple services to [Status-Severity]
Example: Status change of multiple services to minor issue
Description:
Structure: A [Status-Severity] was detected at [timestamp] UTC for [Servicename-Long1] ([Region1]), [Servicename-Long2] ([Region2]), [Servicename-LongN] ([RegionN]).
Example: A minor issue was detected at 2024-01-23 10:45 UTC, for Elastic Load Balancer (EU-DE), Object Storage Service (EU-NL).
Case 2-B) multiple affected services - status update msgs
Title:
Structure: Update published for: [Incident-Title]
Example: Update published for: Reduced performance for ECS due to network issue
Description:
Structure: An update was provided at [timestamp] UTC for [Servicename-Long1] ([Region1]), [Servicename-Long2] ([Region2]), [Servicename-LongN] ([RegionN]): [Incident-Status] - [Update-Msg]
Example1: An update was provided at 2024-01-23 10:45 UTC for Cloud Container Engine (EU-DE), Elastic Load Balancer (EU_NL), …: Investigation started - Update for CCE: Issue Fixed.
Example2: An update was provided at 2024-01-23 11:45 UTC for Cloud Container Engine (EU-DE), Elastic Load Balancer (EU_NL), …: Investigation started - Update for ELB: Investigation started.
Example3: An update was provided at 2024-01-23 11:59 UTC for Cloud Container Engine (EU-DE), Elastic Load Balancer (EU_NL), …: Resolved- Issue resolved and services are again running normal.
Case 3-A) Maintenance planned
Title:
Structure: Maintenance planned for [ServicenameShort1], [ServicenameShort1], [ServicenameShortN]
Example: Maintenance planned for ELB, OBS, EVS
Description:
Structure: A maintenance is planned for [Servicename-Long1] ([Region1]), [Servicename-Long2] ([Region2]), Servicename-LongN between [StartTime] UTC and [EndTime] UTC: [IncidentSummary]
Example: A maintenance is planned for Object Storage Service (EU-DE), Elastic Volume Service (EU-NL) between 2024-01-23 10:45 UTC and 2024-01-23 12:00 UTC: We upgrade something important.
Case 3-B) Maintenance starts
Title:
Structure: Maintenance started for [ServicenameShort1], [ServicenameShort1], [ServicenameShortN]
Example: Maintenance started for ELB, OBS, EVS
Description:
Structure: A maintenance started for [Servicename-Long1] ([Region]), [Servicename-Long2] ([Region]), Servicename-LongN planned until [EndTime] UTC: [IncidentSummary]
Example: A maintenance started for Object Storage Service (EU-DE), Elastic Volume Service (EU-NL) planned until 2024-01-23 12:00 UTC: We upgrade something important.
Case 3-C) Maintenance ends
We send no RSS Feed Msg for the Maintenance End