cds-snc / notification-planning-core

Project planning for GC Notify Core Team
0 stars 0 forks source link

Change NewRelic plan #405

Open jimleroyer opened 2 months ago

jimleroyer commented 2 months ago

Description

As a GCNotify developer, I need to negotiate a NewRelic plan, So that I can have unlimited full admin seats, And access to NewRelic support.

WHY are we building?

To get proper access to New Relic with support, and pay less or equal to current fees.

WHAT are we building?

Get a New Relic quote and get through its signing.

VALUE created by our solution

More support, more seats, more features, for the same price.

Acceptance Criteria

QA Steps

jimleroyer commented 2 months ago

We are waiting on operations to know what the official security guidance process. We have our own in CDS but operation said we might have to do the ESDC one. We are checking internally because we had an agreement that we can own this process.

jimleroyer commented 2 months ago

There are ongoing talk internally on how to tackle the esdc guidance process. It seems we did not have a written agreement, hence we need to let internal ops do their due diligence before we can get back to get an exemption. That said, they are trying to make it work for us given that a) we are already using newrelic and b) this is used outside of the gov.ca network (via the macbooks).

jimleroyer commented 1 month ago

We created the #tmp-notify-rcs Slack channel where all participants can talk together and push through.

jimleroyer commented 1 month ago

From Clara:

We're just waiting for an MOU to be written and signed so that we can submit this to ESDC. I'll look into it this morning and give you update shortly

That means we would avoid the long term process as well!

jimleroyer commented 2 weeks ago

We got the MOU back written and signed. Next step for internal ops is to push it through ESDC. The time estimate is that it should get done soon (days to <4 weeks).