Cortex’s developer homepage is a single pane of glass that lays out everything developers need for their daily workflows. On the homepage, you can find all of the services and resources you own, as well as the health status for each one. You can also find your open pull requests and pull requests submitted for your review across GitHub. The homepage also includes Jira tickets that have been assigned to you, as well as your action items from Scorecards and Initiatives. We will be adding support to fetch pull requests for GitLab, Bitbucket, and Azure DevOps in the coming weeks.
Before we get into the features that comprise the developer homepage, it’s important to note that all of the Git features in Cortex use identity mapping. Services use the email address associated with your Cortex account and your GitHub account to connect your Cortex profile with a GitHub user and team.
If the email address or GitHub account you use is not the same as your Cortex login email, then services will not populate. You can connect Cortex with a different account under User Preferences within Settings.
When you select Connect Account via GitHub OAuth, a modal will open where you can enter your information to connect Cortex with the correct account.
The My Catalog tab is driven by service and resource ownership. Here, you’ll see all of the services and resources that appear under the My tabs in the service and resource catalogs. This screen will display any active incidents associated with each entity, as well monitors from APM tools like Datadog. From this tab, you can get a high-level view of the health of all the entities you own.
Under the Reviews tab, you can find all the pull requests that have been assigned to you. Any PRs that have been assigned to you directly or to a team that you belong to will appear here.
My Open PRs
Under the My Open PRs tab, you’ll see all pull requests that you have opened. Next to each pull request, you’ll see which service it’s associated with and its current status. Like Reviews, this data isn’t tied to actual services in Cortex, but a specific Cortex/GitHub user.
Within the Issues tab, you’ll find Jira tickets that are associated with your email address. Cortex runs a JQL query against your Jira instance to populate tickets that have been assigned to your associated account.
The Action items tab pulls in all the action items from scorecard rules and ongoing initiatives. This screen will mirror the My Action Items page.
On-call and Insight
The On-call block at the top of the homepage pulls in on-call information from PagerDuty or Opsgenie. Like other features of the homepage, Cortex will use your email address to determine your upcoming or current on-call status.
The Insight blocks are computed using the Cortex recommendation engine. The recommendation engine will promote quick wins that it finds within your scorecards and initiatives. For example, an Insight might highlight that a service has one rule remaining to achieve the next level.
The intelligent recommendations promoted within Insight will change over time, as you make progress on your goals and as the recommendation engine is optimized.
Article is closed for comments.