Common Issues with Configuring Honeycomb | Honeycomb

Common Issues with Configuring Honeycomb

If you need to troubleshoot configuring your Honeycomb Environments and Teams, explore these solutions to common issues.

Tip
To ask questions and learn more, visit our Support Knowledge Base or join our Pollinators Community.

Environments 

Troubleshoot issues related to managing Environments.

When you try to delete an Environment, the delete button is disabled 

Check that you have typed in the correct unique identifier of the environment you want to delete. It should be listed in parentheses in the prompt for the field.

API Keys 

Troubleshoot issues related to API Keys.

You cannot see the value of your API key 

For security reasons, the full, 64-character API key is only available when you first create the API key. Only the non-sensitive first 32 characters of the API Key (a region-specific prefix and the key’s identifier) are available in the Honeycomb UI thereafter.

If you have misplaced the full API key, we recommend that you disable or delete the key, and create a new one.

Team Access 

Troubleshoot issues related to configuring access for Teams.

Google SSO 

Troubleshoot team member authentication access that uses Google Single Sign-on (SSO).

Team members encounter a message stating that no user accounts match their credentials 

When attempting to log in to Honeycomb using Google SSO, users may encounter a message stating that no accounts match their user credentials:

Honeycomb login screen with message stating that no accounts match the entered user credentials

This message appears when the user’s team has configured Google SSO authentication and the user already has a Honeycomb account associated with email address/password as credentials.

To solve this issue, the user must link their Honeycomb account to their Google account.

After they have linked their Honeycomb and Google accounts, they can log in to Honeycomb using their Google account.

SAML SSO 

Troubleshoot team member authentication access that uses SAML Single Sign-on (SSO).

You receive a SAML assertion error when converting to a SAML SSO team in Honeycomb 

If a “SAML Assertion” error appears, verify that your SSO Identity Provider Audience and Recipient fields match your Honeycomb team settings SSO Service Provider Issuer/Entity ID and Service Provider ACS URL fields. The Audience field should contain: https://ui.honeycomb.io/saml/<team-identifier>, while the Recipient field should contain: https://ui.honeycomb.io/auth/callback/saml/<team-identifier>.

When logging in to Honeycomb, users may encounter a message containing instructions to link their accounts:

Image of Honeycomb login with message to login with e-mail and password first, then log in via SAML provider

This message appears when the user’s team has configured SAML SSO authentication and the user already has a Honeycomb account associated with email address/password as credentials.

To solve this issue, the user must link their Honeycomb accounts. To do this, they must authenticate with their existing Honeycomb account before attempting to use SSO to sign in, all within the same session:

  1. Log in to Honeycomb using the existing account’s email and password.
  2. In the same browser, go to the SSO URL provided by your Identity Provider.
Tip
If a user continues to have trouble, they may need to clear their cache. Try the same steps in a different browser or in the browser’s Incognito mode.

Microsoft Entra ID SSO 

Troubleshoot team member authentication access that uses Microsoft Entra ID Single Sign-on (SSO).

Honeycomb requires the FirstName, LastName, and Email claims to be populated. If your Microsoft Entra accounts are configured to use a value other than user.givenname or user.surname to represent a user’s first or last name, you may use those other values to populate the corresponding claims instead.