Exploration & Planning
Salto users are able to:
Explore & search their enterprise application configuration
Find hardcoded values to identify and plan bulk changes
Understand how different configuration elements relate to one another, e.g., identify dependencies, see who reads-from or writes-to a certain field in the system
Compare and identify changes across different environments, e.g., staging and production
This set of capabilities exposes the impact a certain configuration change may have on other areas of the application, thus helping admins and developers to better plan their work and deliver it to production with confidence. Learn more
Change Log & Documentation
Salto automatically tracks all environment changes, regardless of how they were made are accessible in the environment’s 'Change Log' tab which provide the following values:
Compliance - Any configuration change is represented by a change log operation and can be linked to the relevant task(s) in your ticketing system. This links the business requirement with the actual configuration change that was made in order to implement it.
Root Cause Analysis - In the event of an incident, admins and developers can leverage the documentation trail to better understand recent configuration changes and pinpoint the underlying issue faster.
Backup & Restore - It is possible to compare the current configuration version with a previous point in time and restore selected elements to their previous values, e.g. post sandbox refresh.
Visibility and Control - Salto tracks and documents all of the configuration changes so that teams can always know who made a change, when, and what exactly has changed.
Deployments & Change Management
Salto users are able to deploy changes to their enterprise applications’ configuration. Deploying configuration changes from Salto introduces the following benefits:
Built in environment comparison tools can be used in order to define the scope of the deployment based on the differences between two environments.
Get deployment scope recommendations based on Salto’s ability to detect the relationships between different configuration elements, e.g., when adding a certain script to the scope also add all the fields that are being accessed by that script.
Revert previously deployed changes
Make use of Salto’s Find & Replace tools in order to safely and quickly deploy bulk changes. e.g. mass updates to email templates content.
Update your Sandbox or parts of it based on the most recent version of the Production environment.
Integrating Git
Users can take advantage of standard Git-based solutions to collaborate with their teammates and maintain a clear documentation trail of configuration changes across enterprise applications.
In addition, they can enhance change management processes by leveraging pull requests and integrating with CI/CD pipelines for review, testing, and automated deployments. Learn more
Salto Pipelines
Leverage Salto Pipelines to provide visibility and control over your release process. It helps you track where changes are, simplifies promotions and back-promotions, and gives your team a streamlined, unified interface for managing releases.
Monitoring
Salto can be configured to trigger a user notification upon changes in sensitive configuration areas, e.g. get notified via email or slack whenever a field that is integrated with another enterprise application gets deleted or modified.
Notifications include information about:
What has changed.
How it was changed, including a comparison (diff) between the previous and current values.
Who changed it.
When creating a monitor, users can specify:
Types and/or instances that need to be tracked.
Type of change to watch for (e.g., addition, modification, or deletion)
Source of the change via Salto deployment, directly in the service, i.e. out-of-band changes or both