Kloudfuse

Integrating Kloudfuse with NeuBird makes your logs and metrics available to investigations.

NeuBird authenticates with a service account token issued from Kloudfuse. A service account is scoped by policy, identifiable in your audit logs, and revocable on its own.

You also need your Endpoint URL, the base URL of your Kloudfuse instance.

Step 1: Create a service account

1. In Kloudfuse, open Admin and select Service accounts.

   

2. Click Create service account.

   

3. Give it a name such as neubird-service-account and set Role to Viewer, then click Save. Viewer is enough — NeuBird only reads.

   

Step 2: Create an access policy

1. Back in Admin, select Policies.

   

2. Click Create policy.

   

3. Name it, for example neubird-access-policy, then set the scopes. Access type of All with Logs and Metrics selected covers what NeuBird queries; include Events and APM if you want those correlated too.

   

   Click Create.

Step 3: Attach the policy to the service account

1. Open the service account, choose your policy under Service account policies, and click Add policy.

   

2. Confirm the Effective policies table shows the streams you expect.

   

Step 4: Create the token

1. Click Create token, give it a name such as neubird-service-access-token, and click Create token.

   

   Leave No expiration off if your policy requires rotation — but note the connection stops working when the token expires, with no warning beforehand.

2. Copy the token immediately.

   

   Caution

   Kloudfuse shows the token once. Copy the entire value, including the <token-name>:glsa_ prefix — the part before the colon is required, not a label. Treat it as a password.

Add the Connection in NeuBird

1. In NeuBird, go to Settings > Connections and click Add Connection.
2. Select KloudFuse.
3. Enter a Name and, optionally, a Description.
4. Fill in the fields below and click Save.

Connection Fields

Field	Required	Description
Name	Yes	A descriptive name for this connection
Description	No	Optional note about what this connection is for
Endpoint URL	Yes	Base URL of your Kloudfuse instance, e.g. https://kloudfuse.example.com
Service Account Token	Yes	The full token from Step 4, including the :glsa_ portion

Troubleshooting

Symptom	Likely cause
401 on validation	The token was truncated — the value must include everything before and after the colon
Validation succeeds, no data appears	The policy attached to the service account does not cover Logs or Metrics
Worked previously, now failing	The token expired, or the policy was detached from the service account

---

For general instructions on creating and managing connections, see the Connections Overview.