[SERVER-73592] Configure the Chart snapshot to be sent to the SDP members Created: 03/Feb/23  Updated: 25/Feb/23  Resolved: 14/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Iryna Zhuravlova Assignee: Tausif Rahman (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

As an SDP Engineer, I would like to receive a weekly or bi-weekly email update on how the Local Dev Metrics are changing. 

 

Set up a weekly or bi-weekly delivery of the Dev Workflow Charts Dashboard snapshot to be sent to the SDP members via email.



 Comments   
Comment by Tausif Rahman (Inactive) [ 14/Feb/23 ]

We are going to have a monthly metrics meeeting to go over this https://docs.google.com/document/d/1q5MoWt0LiArh7lxU5mliBgPJzL0dYC2u2xpGyTdwUE4/edit#

 

Comment by Tausif Rahman (Inactive) [ 09/Feb/23 ]

Going to give this a couple days bc we may combine this dashboard with DAG into a consolidated place.

Comment by Tausif Rahman (Inactive) [ 09/Feb/23 ]

There are a few issues with I’ve seen with “exporting the charts and sending them via slack/email”.

  1. Atlas Charts/Dashboards != .pngs & there’s no built-in/programmatic way to get a chart as a png. The other option is to embed the dashboard which is not possible in Slack.
  2. Everything around embedding the actual dashboard requires using some form of authentication in atlas. Using an additional Non-VPC source of auth is risky. I like that right now, if anyone “breaks-in” that means it’s AWS’s fault & I am absolved of guilt.

If the best we can do for visualization comm is a weekly slack message with a link to the dashboard is that good enough? That way our team will just click on the link, log-in w/ okta and see the full dashboard?

If we really want visualizations instead of links, I think we can do this via email, but it’ll require a few things: 

  1. Create a new “view” in Atlas with no PII/Sensitive data & make that restricted view public
  1. Apply the visualizations to the new view to create a new dashboard
  2. Since the data for the “view” is public, we can embed this dashboard directly in an email
  3. We need an sdp email to add to the “metrics publish task” so that we send these embedded emails out via cronjob.

^ Decided not to go this route

Generated at Thu Feb 08 06:25:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.