Certificate status table/list

[katrin-freihofner]

Summary of the problem (If there are multiple problems or use cases, prioritize them)
As someone responsible for managing TLS/SSL Certificates
I want be able to view a table of all my monitors with SSL certificates, the expiration of those certificates and if any are in A"alert" state
So that I have a single source of truth for my certificates that I can check against and proactively plan updates

Unique page in Uptime that shows a table
Table contains Monitor Name, SSL/TLS Certificate yes/no, Expiration Date & time, alert state column
Alert state column rules match triggers for sending an actual alert

[elasticmachine]

Pinging @elastic/observability-design (design)

[katrin-freihofner]

Certificates page design

Quick walk-through

Navigating to the certificates page

From the overview

There is a button in the top right corner of the monitor list panel.

From the monitor details

There is a button next to the certificate information. (Only there is the certificate information is available)

[andrewvc]

Looks great! I think you're right about the search box, we could add one that searches CommonName, SAN, monitor.url.full and monitor.name as a start. I'd think that would make sense vs. the kuery bar style where we break it out by field. It would intuitively yield what you want 99% of the time.

[katrin-freihofner]

Update from yesterdays meeting:

• We will be able to show expired certificates (red indicator in status column)
• We are going to use the EuiDatagrid instead of a table. By default, we are going to display the following columns: Status, common name, monitors, issuer, and expiration date.
• Columns can be changed and sorted. (We don't need the density or fullscreen functionality)
• By default, the list is sorted by the expiration date
• We are going to add a searchbox. It will be a text search.
• The headline should say "certificates"

[katrin-freihofner]

Figma link
Prototype link

[andrewvc]

@katrin-freihofner to update this with I believe where we finally wound up on the design changes:

1. We will not use a datagrid, but rather a table
2. We will use expanding table rows, as on the overview page, to show SHA1/SHA256/MD5 fingerprints as well as the full monitor list.

Did I miss anything @drewpost @katrin-freihofner ?