Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

Description of what we're building, the end goal and how we'll go about it.

Acceptance Criteria 

Customer looking at the notifications eventlog to have a consolidated view of all alerts sent from his OSD clusters (rather than having to look at each cluster's history separately).

Current display only shows there was an alert / notification sent with no option to view the content of the message figure out what is it about.
From customer perspective this screen as it is now - is useless

Checklist

Open Questions

Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed. 

1. Which kind of details does the customer want in this view? The RAW payload?
2. For example, for Slack notifications we simply can show the content of the message, but we cannot know which channel was the notification sent to because that information is encoded in Slack's URL. Would this be acceptable?
3. Would the customer want to see the recipients of the emails? Does this have any privacy/security concerns?

Considerations

• We discussed that one potential solution could be adding a boolean option to event types which then integrated tenants can enable or disable via the internal administration panel, so that tenants can control that by themselves. That way the people who produce that data, and really know if the data contains sensitive stuff or not, can make the best decision about it.