Notifications are built into Cortex to help users stay on top of changes within their environments and within the platform. There are several types of notifications:
Initiative creation - teams notifications alert teams when an initiative is created that impacts one of the team's services. The notification will go to Slack channels associated with that team, and go out every 10 minutes. The notifications will include action items associated with entities owned by that team.
Initiative creation - users notifications go to specific users when a team is not listed as the owner.
Initiative reminder notifications will alert you seven days and one day before an initiative’s target date. This notification will tell you how much time remains in the initiative, as well as your uncompleted action items.
Entity evaluation notifications go out when you have updated an entity, and that entity is reevaluated by a Scorecard. This alert will tell you whether the score for that entity has increased or decreased. You will not receive a notification if the score is unchanged after we process the changes.
Weekly report - Users notifications go out on Mondays with information about entities associated with that user. These notifications will let users know how their entities are performing against Scorecards and Initiatives. This will include scores that improved or dropped, pull requests that are open and waiting for your review, and Jira tickets assigned to you.
Weekly report - Teams notifications go out on Mondays to members of a Team with information about entities owned by that team. As with the user weekly report, these notifications detail how entities performed against Scorecards and Initiatives. The Weekly report - Teams notification also includes information about who is on call for services owned by that team.
On-call change notifications are sent out when the appointed user on call changes. These notifications will go about an hour before the on-call shift. On-call reminder notifications are sent to the user on call for a given entity 7 days and 1 day before the on-call shift. Reminder notifications don’t have to go to a designated service owner.
Integration configuration error notifications will also notify users who can edit settings if the configuration for an integration has been changed, and is no longer valid. Cortex runs a nightly cron job that checks to ensure configurations are valid; when it detects a change that makes the configuration invalid, admins will receive a notification around 7 am PT alerting them to fix it.
Onboarding notifications will go out to users after they log into Cortex for the first time. This notification will welcome users to the platform and will provide information to get started, including an introduction to the catalog. Users will also receive an onboarding message two weeks into using Cortex with information on using the developer homepage, and a final notification six weeks into using Cortex with more in-depth information on other tools, such as the API explorer and Dependency graph.
Unsubscribing
Users also have the ability to unsubscribe from any of these notification types. To access Notification subscriptions, navigate to Settings. You’ll find Notification subscriptions under Preferences. To unsubscribe, select the toggle next to the appropriate notification; you can re-subscribe to any notification type the same way.
You also have the ability to adjust workspace notifications — this is available in the Notifications page under Workspace. From this page, you have the ability to turn notifications on or off for all users, or for email users. Email users are users whose email address is in Cortex, but who have not yet logged into the platform.
Comments
0 comments
Article is closed for comments.