Skip to content

Sumo Logic

Connecting Sumo Logic to NeuBird makes your logs, metrics, and traces available to investigations.

NeuBird authenticates with a Sumo Logic access key, which is an Access ID and Access Key pair created under your account’s security settings.

  1. Open Access Keys: in Sumo Logic, go to Administration, and under Account Security Settings select Access Keys.

    Sumo Logic Administration menu with Access Keys under Account Security Settings

  2. Add a key: click + Add Access Key and complete the dialog.

    • Name: a descriptive name, for example neubird-api-access-key.
    • Allowed CORS Domains: leave empty. NeuBird calls the API from its own backend, not from a browser.
    • Scopes: Default grants the key everything your roles allow. To narrow it, choose Custom and grant read access to the data you want NeuBird to search.

    Sumo Logic Add New Access Key dialog

  3. Copy both values: Sumo Logic shows the Access ID and Access Key once. Copy both before closing the dialog, then click Done.

    Sumo Logic showing the generated Access ID and Access Key

Sumo Logic runs separate deployments per region, and the API endpoint differs for each. The address bar of your Sumo Logic session tells you which one you are on: https://service.sumologic.com is the default deployment, whose API endpoint is https://api.sumologic.com. Other regions carry a prefix — https://service.us2.sumologic.com corresponds to https://api.us2.sumologic.com.

You can paste either form. NeuBird rewrites service. to api. and adds the api. prefix when it is missing, so both of these resolve to the same endpoint:

  • https://service.sumologic.com
  • https://api.sumologic.com

Any path you include is ignored — NeuBird appends the API paths it needs.

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

NeuBird validates the credentials by calling Sumo Logic’s account owner endpoint, so a key that cannot reach it fails immediately rather than at first search.

FieldRequiredDescription
NameYesA descriptive name for this connection
DescriptionNoOptional note about what this connection is for
API EndpointYesYour deployment’s endpoint, for example https://api.sumologic.com
Access IDYesThe Access ID from Step 1
Access KeyYesThe Access Key from Step 1
SymptomLikely cause
Validation fails on the URLThe endpoint is missing a scheme or a host. Include https://
Validation fails with an authentication errorThe Access ID or Access Key is wrong, or the key was deactivated after 30 days unused
The connection worked and then stoppedThe access key was auto-deactivated for inactivity, or deleted on the Access Keys page
Searches return nothingThe key’s scopes, or the roles behind them, do not grant read access to the data you are searching

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