You can have several projects in Lightstep Observability. For example, you might have one project for your development environment and one for production. Or you may have projects for different areas of your application while they’re in development.

Many things in Lightstep Observability are project-specific, meaning they apply only to the project and won’t be applicable to everything in an Enterprise’s account. The following are specific to projects:

  • Access Tokens: Tracers use access tokens to send data to your Microsatellites.
  • Workflow links: Workflow links allow you to add links to the Trace view to information you may need while resolving an incident.
  • Deployment Markers: When you use an instrumentation attribute to denote deployments to an environment, Lightstep Observability allows you to see how your deployments may have affected performance in your system.
  • Metric details: You can view all metrics reporting to this project. Click on a metric to add or edit its details.

    When you add or change a metric’s details, you can choose to apply those changes to all projects.

  • Service name attribute for metric data: Lightstep Observability’s Change Intelligence uses a service name tag in your metric data to map that data to your trace data and find components in your system whose performance changed at the same time as a metric change.
  • Instrumentation Quality Score: Lightstep Observability analyzes the instrumentation on your services and provides a score to let you know where your instrumentation might need improvement. The better your instrumentation, the better Lightstep Observability can help you find and mitigate issues. To ensure that all your services use the specific attributes needed by your system, you can register custom and environment attributes with Lightstep Observability. If these are missing from a service, Lightstep Observability will report it and provide the code needed to add it to your service.
  • Inferred Services: When you use attributes to mark requests going to external services (like a database), Lightstep Observability can report on performance of those services.
  • Microsatellites: Microsatellites collect the span data sent from your tracers. You can enforce a project to only accept data from your on-premise Microsatellites. This can be helpful for projects that are for a production environment.

    Lightstep recommends having a separate project for each environment (for example, prod and dev), and then using single-project mode on your Microsatellites to create a dedicated pool for each project. Doing so also avoids having to send access tokens from your tracers.

  • Data retention policy: Determine how long your span data lives in Lightstep Observability. By default, data is saved for 28 days. Depending on your Lightstep Observability plan, you can increase that time to match your company’s data retention policy, up to 2 years.

Access a project

You load the data and settings for a project from the Projects icon in the navigation bar. Select the project to load.

Create a project

You create and manage projects from the Project & Users tab of the Account Settings page. Projects are listed in alphabetical order.

To create a project:

  1. From the navigation bar, go to Account > Account Settings and select the Projects & Users tab.

  2. Click New Project, enter a name for the project and click Confirm. The project is added to the list of projects.

Adjust project settings

You manage project settings from the Settings icon in the navigation bar.

Delete a project

You delete a project from the Account Settings page.

To delete a project:

  1. From the navigation bar, go to Account > Account Settings and select the Projects & Users tab.

  2. Click Delete.
  3. Enter the project name as it’s shown in the project list and click Delete <project name>.