Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/opslevel/backstage-plugin

OpsLevel's Service Maturity plugin for Backstage
https://github.com/opslevel/backstage-plugin

backstage maturity npm npm-module npm-package npmjs

Last synced: 26 days ago
JSON representation

OpsLevel's Service Maturity plugin for Backstage

Awesome Lists containing this project

README 

        
[![Overall](https://img.shields.io/endpoint?style=flat&url=https%3A%2F%2Fapp.opslevel.com%2Fapi%2Fservice_level%2FSX_5tBBV3PXtQcTEe4j6kGw_Sm0ys-piO0swtoWKCwo)](https://app.opslevel.com/services/backstage_plugin/maturity-report)

[![npm](https://img.shields.io/npm/v/@opslevel/backstage-maturity)](https://www.npmjs.com/package/@opslevel/backstage-maturity)



# OpsLevel Maturity Plugin



This plugin helps you leverage OpsLevel's powerful maturity features with your existing Backstage catalog. An OpsLevel API Key is required to use this plugin.



![](docs/rubric.png)



![](docs/maturity-on-service.png)



![](docs/maturity-report.png)



[OpsLevel](https://www.opslevel.com/) gives platform engineers and DevOps leaders the tools to drive service maturity for their teams. We understand that maturity features alongside your software catalog are critical to a culture of service ownership. Which is why we’ve made our maturity features available to Backstage users within their existing service catalog.



OpsLevel uses [Checks](https://www.opslevel.com/docs/getting-started-with-checks) to measure Service Maturity. Checks let you explicitly define how you want your services to be built and operated.

With OpsLevel Checks, you can verify that services:

* Are using a particular version of a library or framework

* Have migrated to a new third-party tool (e.g., all services use Splunk)

* Meet certain operational requirements (e.g., all Tier-1 services have an on-call schedule)



And a whole lot more.



Paired with our [Rubric](https://www.opslevel.com/docs/getting-started-with-rubrics), Checks allow you to get a holistic view of the health of your software ecosystem. This allows you to not just catalog and create new services but also take action to prevent outages and vulnerabilities.



With the plugin, you can view maturity progress in context with the rest of your service information in Backstage. If you want to dig deeper, you can toggle back to OpsLevel from Backstage to see more health metrics through our Rubric or Check Reports.



**Note**: Due to the current configuration of API Tokens in OpsLevel, Backstage needs administrator permissions to retrieve all account data. We recommend strongly to only use this plugin if your Backstage instance is exposed only to internal users via VPN.



## Install Plugin



```bash

yarn add --cwd packages/app @opslevel/backstage-maturity

```



Setting up this plugin requires the following changes to the `app-config.yaml` file:



### Set Up Proxy Configuration



Add a proxy configuration for OpsLevel. Replace `` with a token from https://app.opslevel.com/api_tokens (or, if you're running a self-hosted OpsLevel instance, the `/api_tokens` page on your OpsLevel instance).



```yaml

proxy:

  endpoints:

    '/opslevel':

      target: 'https://app.opslevel.com'

      credentials: 'dangerously-allow-unauthenticated'

      headers:

        X-Custom-Source: backstage

        Authorization: Bearer 

      allowedHeaders: ['GraphQL-Visibility']

```



If you're running Self-Hosted OpsLevel, replace `target` with your URL.



> :warning: **If you are using an authentication solution with Backstage**: Ensure that it does not interfere with the HTTP headers going through this proxy. If requests to OpsLevel seemingly inexplicably fail with a HTTP 401 (Unauthorized) response, but you have confirmed that your API token is valid, this is one possible root cause. Due to the customizable nature of Backstage, the support we will be able to offer in such cases will be limited.



### Set Up the Base OpsLevel URL



```yaml

opslevel:

  baseUrl: 'https://app.opslevel.com'

```



If you're running Self-Hosted OpsLevel, replace `baseUrl` with your URL.



### Add Route & Global nav



Update `packages/app/src/App.tsx`



```jsx

import { OpslevelMaturityPage } from '@opslevel/backstage-maturity';

```

```jsx

    }/>

```



Update `packages/app/src/components/Root/Root.tsx`



```tsx

import CheckCircleOutlineIcon from '@material-ui/icons/CheckCircleOutline';



```

```tsx

        

```



### Add Tab for Maturity to Services



In `packages/app/src/components/catalog/EntityPage.tsx` import the plugin and add it to `serviceEntityPage`



```tsx

import { EntityOpsLevelMaturityContent } from '@opslevel/backstage-maturity';

```

```tsx

    

      

    

```



### Next Steps



Visit the Maturity tab in Backstage to get started. Once you have synced data from Backstage to OpsLevel, you will likely want to set up auto-syncing of data using the [backend-plugin](https://github.com/OpsLevel/backstage-plugin-backend).



## Troubleshooting



### 403 API Requests



Please validate that you do not have any middleware set up in Backstage that could be removing headers from the request by the Backstage proxy.



### 404 API Requests



If you are receiving 404s or any non-200 response codes, it is possible that there is a network firewall preventing Backstage from accessing the OpsLevel instance.



You can rule this out by using [Postman](https://www.postman.com/downloads/) or another tool to simulate the request from the machine running Backstage.



Sometimes it can be hard to set up a tool in environments running Backstage, in which was you can use `curl` to make the request with your API token.



You will need:



- `[[api_token]]` - created from the [api token page](https://app.opslevel.com/api_tokens). It should look like `JEgofP1igAiemSBZ6BJmFma0P8k4FCnIh9sm`.



```sh

curl 'https://app.opslevel.com/graphql' -X POST -H 'content-type: application/json' -H 'graphql-visibility: internal' -H "Authorization: Bearer [[api_token]]" --data-raw '{"operationName":"requestApplicationConfigs","variables":{},"query":"query requestApplicationConfigs {\n  elasticsearchEnabled\n  environment\n}"}'

```



If this responds with a successful response, it means that the connection is available and that your token is valid. A successful response looks like:



```

{

  "data": {

    "elasticsearchEnabled":true,

    "environment":"production"

  }

}

```