Honeycomb users who had a team before the Honeycomb Environments and Services change have a Classic environment. Previously, datasets in Honeycomb were independent, unconnected buckets of information. This dataset-only data model is known as Honeycomb Classic.
Honeycomb now supports an expanded data model with Environments and Services as groupable, relational structures.
Future product updates will ONLY support the Environments and Services model. For example, Service Map only supports datasets within an Environment. We encourage teams to migrate in order to use these new features.
In the left navigation menu, reference the label below the Honeycomb logo. The Honeycomb Classic environment has a Classic label with a gray background.
In Honeycomb Classic, to accommodate data that traversed multiple services, like traces, often meant sending all data to a single Dataset.
The Environments and Services model allows you to define and visualize data across Datasets or an Environment. The diagram reflects the new data model where a team can have multiple environments, such as Non-Prod and Prod, and group multiple datasets under each environment.
Benefits of migrating from Honeycomb Classic to Honeycomb include:
Explore migration preparation, and preview migration documentation.
Join the #discuss-hny-classic channel in our Pollinators Community Slack to ask questions and learn more.
For Pro and Enterprise users, contact Support via support.honeycomb.io, or email at firstname.lastname@example.org.
Did you find what you were looking for?