Set up a Grafana connector
Capabilities
Resource | Sync | Provision |
---|---|---|
Accounts | ✅ | |
Organizations | ✅ |
Available hosting methods
Choose the hosting method that best suits your needs:
Method | Availability | Notes |
---|---|---|
Cloud-hosted | ✅ | A built-in, no-code connector hosted by ConductorOne. |
Self-hosted | ✅ | The Grafana connector, hosted and run in your own environment. |
Gather Grafana credentials
Each setup method requires you to pass in credentials generated in Grafana. Gather these credentials before you move on.
To set up the Grafana connector, you’ll need:
- The username and password for a Grafana account with admin-level permissions
- Your Grafana instance URL
That’s it! Next, move on to the instructions for your chosen setup method.
Set up a Grafana cloud-hosted connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- Access to the set of Grafana credentials generated by following the instructions above
In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Grafana and click Add.
Don’t see the Grafana connector? Reach out to support@conductorone.com to add Grafana to your Connectors page.
Choose how to set up the new Grafana connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Paste your Grafana instance URL into the Instance URL field.
Paste the Grafana admin-level account’s username and password into the Username and Password fields.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Grafana connector is now pulling access data into ConductorOne.
Set up a Grafana self-hosted connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- Access to the set of Grafana credentials generated by following the instructions above
When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.
Step 1: Configure the Grafana connector
In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Grafana connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.
Step 2: Create Kubernetes configuration files
Create two Kubernetes manifest files for your Grafana connector deployment:
Secrets configuration
# baton-grafana-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-grafana-secrets
type: Opaque
stringData:
# ConductorOne credentials
BATON_CLIENT_ID: <ConductorOne client ID>
BATON_CLIENT_SECRET: <ConductorOne client secret>
# Grafana credentials
BATON_HOSTNAME: <Grafana instance URL>
BATON_USERNAME: <Grafana account username>
BATON_PASSWORD: <Grafana account password>
See the connector’s README or run
--help
to see all available configuration flags and environment variables.
Deployment configuration
# baton-grafana.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-grafana
labels:
app: baton-grafana
spec:
selector:
matchLabels:
app: baton-grafana
template:
metadata:
labels:
app: baton-grafana
baton: true
baton-app: grafana
spec:
containers:
- name: baton-grafana
image: ghcr.io/conductorone/baton-grafana:latest
imagePullPolicy: IfNotPresent
envFrom:
- secretRef:
name: baton-grafana-secrets
Step 3: Deploy the connector
Create a namespace in which to run ConductorOne connectors (if desired):
kubectl create namespace conductorone
Apply the secret configuration:
kubectl -n conductorone apply -f baton-grafana-secrets.yaml
Apply the deployment:
kubectl -n conductorone apply -f baton-grafana.yaml
Step 4: Verify the deployment
Check that the deployment is running:
kubectl -n conductorone get pods
View the connector logs:
kubectl -n conductorone logs -l app=baton-${baton-grafana}
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Grafana connector to. Grafana data should be found on the Entitlements and Accounts tabs.
That’s it! Your Grafana connector is now pulling access data into ConductorOne.