Notifications

Firefly's Notifications system keeps you informed about important changes in your cloud infrastructure. Whether it's a configuration drift, a policy violation, or a change in asset status, Firefly ensures you and your team receive timely alerts through your preferred communication channels.

Overview

Notifications in Firefly are designed to help you stay on top of critical events in your environment. When there are changes to the state or configuration of your assets, Firefly can notify you via Slack, Microsoft Teams, Opsgenie, Torq, PagerDuty, Webex, Google Chat, or custom webhooks. This enables rapid response to issues, improved governance, and better collaboration across teams.

Notifications can be tailored to your needs—choose which events trigger alerts, where they are sent, and who receives them. This flexibility ensures you only get the information that matters most to your operations.

Types of Notifications

Firefly supports a variety of notification types, including:

• Drift Detection: Alerts when a resource's actual state diverges from its IaC definition.

• IaC Status Change: Notifies when an asset's status changes (e.g., from Codified to Unmanaged or Ghost).

• Policy Violation: Informs you of governance or guardrail rule violations.

• New Resource Created with ClickOps: Alerts when a resource is created outside of IaC (manual/console changes).

• Workspace Run: Notifies about IaC runs or deployments.

• Workspace Guardrail Violation: Alerts for violations detected at the workspace level.

You can view the timestamp and creator of each notification subscription, making it easy to audit who set up which alerts and when.

Notification Criteria and Customization

When creating a notification, you can specify detailed criteria to control when and how notifications are sent:

• Event Type: Choose the type of event (drift, policy violation, etc.)

• Data Source: Select which cloud providers or IaC sources to monitor

• Asset Type: Filter by resource type (e.g., EC2, S3, GKE, etc.)

• Tags: Use tags to target specific resources or environments

• Owner: Notify based on resource ownership

• Location: Filter by region or cloud account

• Destination: Choose where notifications are sent (Slack, Teams, etc.)

This granularity allows you to create highly targeted notification rules. For example, you might set up a rule to alert your SRE team about drifts in production AWS accounts, while sending policy violation alerts to your security team.

Supported Notification Integrations

Firefly integrates with a wide range of notification platforms. For detailed setup instructions, see the Notification Integrations documentation:

• Slack
• Microsoft Teams
• Google Chat
• Webex
• PagerDuty
• Opsgenie
• Torq
• Webhook

Each integration guide covers prerequisites, setup steps, features, best practices, and troubleshooting tips.

How to Create and Manage Notifications

1. Navigate to the Notifications Page: Go to the Notifications section in the Firefly UI.

2. Add New Notification: Click "Add new" to open the notification creation form.

3. Configure Notification:

   • Select the event type (e.g., Drift Detection, Policy Violation)

   • Optionally provide a name for the notification

   • Set criteria (data source, asset type, tags, owner, location)

   • Choose the destination (Slack, Teams, etc.)

4. Save and Activate: Click "Create" to save the notification. You can enable/disable notifications as needed.

5. Audit and Manage: View all notification subscriptions, including their creator and timestamp. Edit or delete as required.

Tip: You can filter and search your notification rules to quickly find and manage them, especially in large environments.

Best Practices

• Customize for Critical Events: Set up notifications for high-impact events (e.g., drift in production, policy violations) to ensure rapid response.

• Avoid Alert Fatigue: Use tags, asset types, and destinations to avoid unnecessary noise. Route only relevant alerts to each team/channel.

• Test Integrations: After configuring a new integration, test it to ensure notifications are delivered as expected.

• Review Regularly: Periodically review and update your notification rules to match evolving infrastructure and team needs.

• Use Dedicated Channels: Create separate channels or destinations for different alert types (e.g., security, SRE, compliance).

• Secure Webhooks: If using webhooks, ensure endpoints are secured and authenticated.

Example Notification Scenarios

• Governance: Receive alerts when a policy or guardrail rule is violated, helping enforce compliance.

• Drift Detection: Get notified immediately when a resource drifts from its IaC definition, enabling quick remediation.

• IaC Status Change: Be alerted when an asset becomes unmanaged or ghost, so you can investigate and codify as needed.

• ClickOps Detection: Know when resources are created manually, outside of your IaC process.

Cross-References and Further Reading

• Notification Integrations: Setup guides for all supported platforms
• Event Center: Learn how notifications relate to Firefly's event tracking and audit logs
• Disaster Recovery: See how notification rules can help prevent infrastructure failures
• Codification: Automatically bring unmanaged resources under IaC management

Troubleshooting

• Not Receiving Notifications?

  • Check that the integration is active and properly configured

  • Review notification rule criteria for accuracy

  • Ensure the destination (channel, webhook, etc.) is accessible

  • Consult the integration-specific troubleshooting sections

• Too Many Notifications?

  • Refine your criteria (tags, asset types, severity)

  • Use separate channels for different alert types

  • Disable or delete redundant rules

---

Need more help? Contact Firefly support at [e-mail] for assistance with notification setup or troubleshooting.

// This guide provides a comprehensive overview of Firefly's Notifications system, including setup, customization, integrations, and best practices. For integration-specific details, refer to the linked documentation above.