Help Center
Help Center
  • Getting Started
    • What is Haystack?
    • Quick Start
      • Account Setup
      • Roles
        • For Executives
        • For Managers
        • For Product
  • Setup
    • Integrations
      • Jira
      • GitHub Cloud
      • GitHub Enterprise
      • GitLab
      • Bitbucket
      • Slack
    • Organization
      • Investments
      • Deployments
      • Invite users
      • Exclusions
    • Teams
      • Map members
      • Sprint success metric
      • Capacity
      • Alerts
      • SLAs
      • Risks
  • Features
    • Issues
    • Pull Requests
    • Epics
    • Retrospective
    • Release Notes
    • Investments
    • Alerts
    • Customizable Widgets
    • Flexible Reports
    • Team Metrics
    • List of All Metrics
    • API
    • Embedded reports
  • Admin
    • Security & Privacy
    • Data Sync
      • How to setup faster data sync for JIRA?
  • FAQ
    • Can I track Dora metrics?
    • What is Status Category?
  • Guides
    • First Principles of Engineering Metrics
    • Engineering Metrics (Video Series)
    • How to Improve Quality?
    • Sprint Planning
    • Daily Standups
    • Retrospectives
    • Identify Bottlenecks
  • Other
    • Changelog
Powered by GitBook
On this page

Was this helpful?

  1. Setup
  2. Organization

Deployments

How to setup Deployment Frequency in Haystack

Last updated 12 months ago

Was this helpful?

Quickly measure how fast your teams are deploying and delivering value to customers by setting up deployments on Haystack. To configure deployments, follow the below steps

1. Head to Deployment Settings

Head to settings by

  • clicking gear icon on first sidebar

  • clicking Deployments on second sidebar

2. Click on "New Service"

3. Provide a name and description for your service

4. Create an environment for Deployment

Typically companies have 2 environments

  • staging environment

  • production environment

You'd want to set both of these separate to measure them accurately

5. Setup how to identify each deployment

Haystack can identify deployments based on different identifiers

  1. Commit - tags each commit as a deployment

  2. Pull Request - tags each pull request as a deployment

  3. GitLab Deployments - tags GitLab deployments as a deployment

Each option allows you to have conditional where clauses. You can filter by anything from Author, Title, Tag, Repository and more.

Typically we suggest our customers to use tag your deployments using Git tags and then use that to identify deployments on Haystack

Best practices for deployment identifier

If you are settings up deployment processes, we suggest tagging each deployment commit with {env} and {version} information. Ex: prod-v1.2.3.

The main reasons are

  1. Commits are source of truth on what production runs.

  2. Commits are easily revertible to old version

  3. Commit tags live together with your code. Finally, a source of truth.

  4. Easy to standardize across teams, projects, repositories.

  5. No data lock-in. Haystack doesn't own the data, you do!

  6. Easily integrated with CI tools like Jenkins, Github Actions, Circle CI, etc.

  7. Complete control. You control when, how, and what system tags your releases.

As long as the whole organization is using Git, it can be standardized across all teams regardless of the tools they use.

6. Confirm the deployments are setup correctly using the preview & save

Gain confidence on your settings by clicking the "8 deployments" link.

7. Track deployments

You will now be able to track your teams deployments over time from both your teams or

metrics page
reports page
deployments