-
Notifications
You must be signed in to change notification settings - Fork 301
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
7ed37d9
commit 54442bd
Showing
2 changed files
with
21 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
|
||
slug: github-integration | ||
description: | | ||
## Why use GitHub Integration? | ||
Implementing a New Relic Service Catalog can unlock considerable benefits, but it requires considerable time and resources. You have to take care of team orchestration, user provisioning, role assignments, and entity ownership delineation. These create a significant threshold for entry. To ease this challenge, consider an automation solution that capitalizes on existing team configurations and relationships maintained in external systems such as GitHub. This simplifies the initial configuration and accelerates the adoption of the New Relic Service Catalog. | ||
## Get started! | ||
Head over to the Integrations and Agents tab in New Relic page and check for Github Integration to get started. | ||
summary: | | ||
Seamlessly adopt New Relic Service catalog with the GitHub Integration. | ||
icon: logo.svg | ||
level: New Relic | ||
authors: | ||
- New Relic | ||
title: GitHub Integration | ||
dataSourceIds: | ||
- github-integration | ||
keywords: | ||
- open source monitoring |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.