---
id: sdo-manual-configuration
title: Manual SDO Configuration
sidebar_label: Manual Configuration
description: Learn how to set up the Software Development Optimization (SDO) Solution. You will manually configure collection and install apps for tool integration, create field extraction rules (FERs) for each supported tool, and install the SDO app.
slug: /help/docs/observability/sdo/set-up-sdo/sdo-manual-configuration/
canonical: https://www.sumologic.com/help/docs/observability/sdo/set-up-sdo/sdo-manual-configuration/
---

These instructions help you prepare and set up the Software Development Optimization (SDO) Solution manually, without using Terraform. You will manually configure collection and install apps for tool integration, create field extraction rules (FERs) for each supported tool, and install the SDO app.

## Prerequisites
Before setting up the SDO solution, you need to complete the following tasks:

* Ensure that you have permissions to configure software and platforms used in your DevOps toolchain that will emit data to Sumo using webhooks (for example, Jira, GitHub, GitLab, Bitbucket, CircleCI, PagerDuty, Opsgenie, and so on).
* If you use Jenkins, ensure that you have access to Jenkins with Manage Plugins permissions.
* Make sure you have access to the Sumo logic web app. The user account associated with a Sumo Logic role needs the following [role capabilities](/docs/manage/users-roles/roles/role-capabilities/):
  * Manage Field Extraction Rules
  * View Fields
  * View Field Extraction Rules
  * Manage Collectors
  * View Collectors
  * Manage Fields
  * Manage Connections
  * Manage Content
* Create a [Sumo Logic access key and ID](/docs/manage/security/access-keys) for the above user.

## Configure collection and install apps

To set up the SDO solution manually, configure collection and install apps for each tool that you want to integrate with this solution. Complete the following instructions for each app integration:

* [Bitbucket](/docs/integrations/app-development/bitbucket)
* [CircleCI](https://circleci.com/docs/sumo-logic-integration/)
* [GitHub](/docs/integrations/app-development/github)
* [GitLab](/docs/integrations/app-development/gitlab)
* [Jenkins](/docs/integrations/app-development/jenkins)
* [Jira Cloud](/docs/integrations/app-development/jira-cloud)
* [Jira Server](/docs/integrations/app-development/jira)
* [Opsgenie](/docs/integrations/saas-cloud/opsgenie)
* [PagerDuty](/docs/integrations/saas-cloud/pagerduty-v2)

## Create new FERs

You will need to manually [create new field extraction rules](/docs/manage/field-extractions/create-field-extraction-rule) (FERs) that map events from tools of your choice to the SDO event schema by using the scope and parse expression from this [JSON file](https://raw.githubusercontent.com/SumoLogic/sumologic-solution-templates/master/software-development-optimization-terraform/sdo_app_artifacts/sdo_fer.txt)
of field extraction rules for each tool.

:::note
When you copy the scope, replace the `$$<toolname>` variable with the source category you configured for the tool you configured when installing apps for tool integration.
:::

## Install the SDO app

Install the Sumo Logic App for Software Development Optimization to use the pre-configured searches and [dashboards](/docs/observability/sdo/install-sdo-app-view-dashboards/) that provide you insights and visibility into your DevOps phases and pipelines.

import AppInstall from '../../../reuse/apps/app-install.md';

<AppInstall/>

## Complete post-setup configurations

After setting up the SDO solution, you can complete post-setup configuration.

## Post-setup configuration

After completing configuration, instrument your DevOps pipeline to specially identify and send build and deploy events in your pipeline to Sumo Logic. These events are correlated with other events in the DevOps lifecycle.

Complete the configuration for the build and deploy tool you use.

### Bitbucket for build and deploy

1. [**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.  <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic).  In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 
1. Search for *Software Development Optimization* collector.
1. Under this collector, click on **Show URL** for the source **Bitbucket Cloud.** Make a note of this **URL** and use this URL to configure the Bitbucket CI/CD Pipeline to collect deploy events:
   * **Deploy**: Follow the steps outlined in [this document](/docs/integrations/app-development/bitbucket#collecting-logs-for-bitbucket-app) to configure the Bitbucket CI/CD Pipeline to collect deploy events.

### Jenkins for build and deploy

1. Install the latest Jenkins plugin as described [here](/docs/integrations/app-development/jenkins#collecting-logs-and-metrics-for-jenkins).
1. [**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.  <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic).  In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 
1. Search for *Software Development Optimization* collector.
1. Under this collector, click on **Show URL** for the source **Jenkins.** Make a note of this **URL** and **Source Category,** you will use these to configure the Jenkins plugin :
    * **Build Pipeline Stages**: Follow directions in [Jenkins](/docs/integrations/app-development/jenkins) to configure the Jenkins Sumo Logic plugin.
    * **Build**: Follow [this](/docs/observability/sdo/jenkins-plugin-build-deploy-events/) doc to modify your Jenkins plugin to explicitly identify, enrich, and send build events to Sumo Logic.
    * **Deploy**: Follow [this](/docs/observability/sdo/jenkins-plugin-build-deploy-events/) doc to modify your Jenkins plugin to explicitly identify, enrich, and send deploy events to Sumo Logic.

### CircleCI for build and deploy

If you're using CircleCI for build and deploy, do the following:

1. [**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu select **Data Management**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.  <br/>[**Classic UI**](/docs/get-started/sumo-logic-ui-classic).  In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. 
1. [Configure a hosted collector](/docs/send-data/hosted-collectors) to ingest CircleCI data into Sumo Logic and call it `Software Development Optimization`.
1. Under this collector, create the following two [HTTP sources](/docs/send-data/hosted-collectors/http-source/logs-metrics):
   * `_sourceCategory=circleci/job-collector`
   * `_sourceCategory="circleci/workflow-collector"`
<br/>Sumo Logic sources, by default, have [multiline processing](/docs/send-data/reference-information/collect-multiline-logs/) enabled. You'll need to disable it here in order to collect structured logs for CircleCI.
1. Copy and save the displayed URLs associated with the sources. You will use this information to upload data.
1. Create Field Extraction Rules:
    1. [**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu select **Data Management**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**. <br/> [**Classic UI**](/docs/get-started/sumo-logic-ui-classic).  In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. 
    1. [Create two FERs](/docs/manage/field-extractions/create-field-extraction-rule) for CircleCI build and deploy events. The parse expression and the scope of the are available [here](https://raw.githubusercontent.com/SumoLogic/sumologic-solution-templates/master/software-development-optimization-terraform/sdo_app_artifacts/sdo_fer.txt).
1. (Optional) In order to use uncertified orbs (partner or community), navigate to your CircleCI platform and perform the below steps:
   1. Go to **Organization Settings > Security** page.
   1. On the **Orb Security Settings** click **Yes** to enable the use of uncertified orbs.
1. Navigate to the CircleCI project environment and create three [environment variables](https://circleci.com/docs/2.0/env-vars/#setting-an-environment-variable-in-a-project) in the project settings of the environment:
   * `CIRCLE_TOKEN = <API personal token created in CircleCi>`
   * `JOB_HTTP_SOURCE = <url of job-collector source created above in step 3>`
   * `WORKFLOW_HTTP_SOURCE = <url of workflow-collector source created above in step 3>`
1. Add the [Sumo Logic orb](https://circleci.com/developer/orbs/orb/sumologic/sumologic) in the configuration file of the project to send custom data elements to Sumo Logic. You can find a sample `config.yml` file [here](https://github.com/SumoLogic/sumologic-orb/blob/main/src/examples/workflow-collector.yml).

### Other tools for build and deploy

The platform is ready to ingest logs and use those to light up corresponding build and deploy events related dashboards.

If you're using tools other than Jenkins and Bitbucket pipelines for build and deploy phases:

1. **Build**: Configure your tool to construct and send events using the build event schema in the section Build Event. 
1. **Deploy**: Configure your tool to construct events using the deploy event schema in the section Deploy Events.