Connect GitLab to Lumigo to identify suspect commits that are likely the cause of issues (available only for Serverless Framework for now).

Get Started

provider:
  environment:
    # Copy your GitLab organization from the repository URL address
    # GitLab organization for example is: "https://gitlab.com/lumigo-io"
    GIT_ORGANIZATION: **GitLab organization**
functions:
  myFunction:
    environment:ֿ
      # Copy your GitLab organization from the repository URL address
      # GitLab organization for example is: "https://gitlab.com/lumigo-io"
      GIT_ORGANIZATION: **GitLab organization**

📘

Don't want to use the "serverless-plugin-git-variables"?

All you need to do is add two more variables:

  • GIT_COMMIT_LONG - A hash value containing the commit Lumigo wants to point to (you can use the "git rev-parse HEAD" command).
  • GIT_REPOSITORY - Name of the repository as it appears in GitLab.

What’s Next

Troubleshoot faster by correlating deployment changes and function trends.

Quickly understand if changes in configuration or code cause an unexpected outcome, such as an increase in the number of invocation failures or degraded performances.

Did this page help you?