Honeycomb uses API keys for a number of different purposes. When sending telemetry data to Honeycomb, the API Key determines the data’s destination Team and Environment. Also, any programmatic request sent to Honeycomb must use an API key.
API keys are set at the Environment level, and apply to all datasets in the Environment.
Locate your Environment’s API Keys:
API keys are managed at the Environment level and found in your Environment Settings. API keys can be created, modified, or deleted only via the UI. You must be a Team Owner to create and edit API keys.
Note: Honeycomb Classic API keys are scoped to all dataset(s) and data in the Classic section. API keys can be created, modified, or deleted only via the UI. Learn more about Honeycomb versus Honeycomb Classic.
Use the Edit API Key modal to modify the API Key’s name, its visibility to team members, its enabled state, and its permissions.
An API key can have any number of the following permissions:
|API Key Permission||Auth API value||Description|
||Send events to Honeycomb. Used as the API Key for getting data in and for the Events API.|
||Create and manage datasets via API. Datasets may also be created implicitly; if an event is sent to Honeycomb specifying a non-existent dataset, an event using an API key with this permission will create a new dataset.|
|Manage Queries and Columns||
||Create and manage queries, columns, derived columns, and query annotations.|
||Execute existing queries using the Query Data API. This feature is available as part of the Honeycomb Enterprise plan.|
|Manage Public Boards||
||Create and manage boards.|
||Create and manage SLOs and their burn alerts. SLO Management is available as part of the Honeycomb Pro and Enterprise plans. SLO Reporting is only available on the Honeycomb Enterprise plan.|
||Create and manage triggers.|
||Create and manage Recipients.|
||Create and manage markers.|
You should use different API keys for different purposes. For example, the API key used to send data in from your production cluster should be different then the API key used for testing; the key used by your build process to create markers should be different from either of those.
Separating these purposes among different API keys allows you to revoke permissions on one key without affecting the abilities of others. It also minimizes the negative effects if a key leaks or is lost.
Did you find what you were looking for?