LogoLogo
What's New?Connect Agent ReleasesBook a DemoPricing
  • Documentation
  • Developers
  • Administration
  • OVERVIEW
    • JFrog Connect Overview
      • Architecture Overview
        • Connect Agent
        • Connect & JFrog Platform
      • Plan Your Update Strategy
        • Software Update Objectives & Concepts
        • Software Update Process & Procedures
  • Get Started
    • Create JFrog Connect Account
    • Log in to JFrog Connect
    • Network Requirements
    • Register Device
  • Manage your Fleet
    • Register Devices at Scale
      • Freeze Image on Device
      • Build Image with Agent
    • Register & Update Device at Once
    • Organize Your Fleet
      • Create Project
      • Move Device between Projects
      • Create Groups
        • Add Device to Group
        • Add Many Devices to Group
        • Change Group Name
        • Delete Group
      • Tag Devices
        • Remove a Tag
      • Remove Many Devices
  • Devices
    • Fleet Overview
      • Filter Devices
      • Locate Devices
    • Device Details
      • Delete a Device
      • Block Updates with Update Trigger
    • Update Connect Agent
    • Delete Many Devices
  • Deployment
    • Create Update Flow
      • Actions
        • Run Command
        • Run Script
        • Deploy File
        • Deploy Docker
          • Use Docker Image
          • Use Docker Compose
          • Get Artifactory Parameters
        • Clone Git Repository
        • Download Artifact
          • Get Artifactory Path
        • Download Release Bundle
          • Get Artifactory Parameters for Release Bundle
        • Update Image
        • Install Debian Package
          • Get Artifactory Parameters for Debian
      • Use Update Parameters
      • On Failure & Rollback
      • Vulnerability Scans
      • Sample Use Case: Build Update Flow for Reuse
    • Deploy Software
      • Set Application & Version
      • Set Alert upon Failure
      • Set Phased Rollout
      • View Deployment Progress
        • Detailed Deployment Information
        • Abort a Deployment
      • Deploy in Groups
      • Sample Use Case: Deploy Docker Images to Devices
  • Tools
    • Remote Tools
      • Use Terminal
      • Open Port Tunnel Session
        • Access with VNC
        • Connect with SSH
        • Access Device Web Applications
      • Run Commands Remotely
        • Run Command as Non-Root User
      • Get Device Files (Fetch Files)
    • Alerts
      • Create Channel
      • Set Webhook
    • Monitor
      • Resource Monitor
      • Process Monitor
  • Releases
    • What's New?
    • Connect Agent Release Notes
  • Troubleshooting
    • Connect Server Status
    • Troubleshoot Topics
      • Device Registration
      • Terminal Troubleshooting
Powered by GitBook
On this page
  • Prerequisite: Alert Channel
  • Aggregation of Alerts
  • Create an Alert on Deployment Failure
  • What’s Next?

Was this helpful?

Export as PDF
  1. Deployment
  2. Deploy Software

Set Alert upon Failure

You can always view the software update status in the Deployments tab. You can also receive an alert if the software update fails. This page describes how to configure an alert upon failure.

PreviousSet Application & VersionNextSet Phased Rollout

Last updated 5 months ago

Was this helpful?

At any time, you can check the status of a software update in the Deployments tab. In addition, you can configure a deployment to send you an alert if the deployment fails. The alert will tell you which device(s) the software update failed on and the time of the failure.

All you have to do is define the channel for the alert, such as an email address or a webhook. This enables you to be informed about failures when you are away from your desk or busy with other things.

Prerequisite: Alert Channel

Before you can create an alert, you need to configure one or more communication channels on which the alerts will be delivered to you. The channel can be an email address or a webhook to a pager device or an application like Slack.

For more information about creating a channel, see .

Aggregation of Alerts

When your software deployment is to a large number of devices, there could be many failures within a short period of time. JFrog Connect’s default behavior is to send an alert for each failure. However, you can choose to aggregate several alerts into a single message by defining an aggregation duration. For example, if you enable alert aggregation and define an aggregation duration of 10 minutes, you will receive only a single notification over a 10 minute period, and each notification will list all the failures that occurred during the 10 minutes.

Since aggregation is per deployment, you will receive separate alert messages for each software update.

Enabling aggregation of alerts for update failures is a two-part process:

  • Enable bundling in the configuration.

  • Set the Aggregation Duration when you configure an Alert upon Update Failure.

Create an Alert on Deployment Failure

To create an alert for a deployment failure, do the following:

  1. Choose an alert channel from the dropdown box and click Apply. You can do this again if you want to define multiple channels. For large deployments, it is recommended to choose channels that have bundling (alert aggregation) enabled.

  1. Set an Aggregation Duration in minutes. The default duration is 10 minutes.

What’s Next?

When you , under Deployment Configuration mark Alert on Deployment Failure.

Learn how you can of your software update.

create a new deployment
view the deployment details
Create Alerts
New Channel