Actioner's Opsgenie app allows you to create incidents and alerts in Slack easily. List the open alerts, manage the lifecycle of the incidents, check the on-call list, and quickly add an override to your on-call schedule.
### Features
- Create, get and close alerts directly in Slack.
- Add responders to alerts and incidents.
- List services, incidents, and timeline entries.
- Hand over your on-call in Slack. Track and collect handover requests in one channel, take the on-call with a single click, and inform your colleagues from one place.
### How it works
Actioner connects your Opsgenie & Slack and brings alert, incident, and on-call management to your teams. You can run any Opsgenie workflow in Slack by calling the Actioner app.
This app also broadcasts on-call handover requests in a dedicated Slack channel. Your team can track on-call requests, on-call changes and quickly take an on-call with a single click.
It's simple enough to get up and run. Install Actioner's Opsgenie app, connect your Opsgenie and Slack and start running Opsgenie workflow in Slack.
Workflows
List alerts
This workflow returns the list of alerts. The distribution of alerts per priority, status, and the team will be shown as charts. You can directly Acknowledge, Unacknowledge, Open in Opsgenie the listed alerts or Add note to these alerts.
Create incident
This workflow allows you to create a new incident with the given parameters. When it's successfully executed, you can easily access the newly created incident.
Add override
This workflow adds an override to the selected schedule for the given time interval.
List incidents
This workflow returns the list of incidents. The distribution of incidents per status and priority will be shown as pie charts. You can directly Resolve or Close the listed incidents.
Take on-call
Run this workflow to take the on-call from the handover request directly.
Suggest someone for on-call handover
Run this workflow to send a DM to your colleagues to respond on-call handover request.
Create alert
This workflow allows you to create a new alert with the given parameters. When it's successfully executed, you can easily access the newly created alert.
On-call handover
Run this workflow to post an on-call handover request to a selected Slack channel. Your colleagues can take on-call or suggest someone directly from Slack.
Add responder to incident
Run this workflow to add responder to a selected incident.
Acknowledge
This workflow allows you to acknowledge and claim the ownership of a selected alert.
Add note
Run this workflow to create a new note for the selected alert.
Add responder to alert
Run this workflow to add responder to a selected alert.
Who is on-call
This workflow allows you to get the current on-call for the selected schedule.
Reject on-call handover
Run this workflow to reject the on-call handover request. The rejection message will be automatically sent to the on-call handover message thread. Also, the user who suggested you will be informed with a DM.
Security & Compliance
Privacy & data governance
Data retention policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. How long we keep your data prior to the deletion of data or termination of the contract between the customer and Actioner depends on the type of data, as described in further detail below:
Account data: Personal data that relates to customers’ relationship with the Actioner, including your workspace details, user accounts and your billing information. We retain your account information for as long as your account is active. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.
Configuration data: Any configuration or personal data that is required by Actioner to be functional for the customer, such as (a) applications and their sub-configurations like workflows, documents or functions, (b) credentials, connections and integrations with the third party providers, (c) identity and access management related personal data. Actioner stores and processes configuration data for the permitted purposes until the customer elects to delete such configuration data via the service and the customer is solely responsible for deleting configuration data.
Usage data: (a) Inputs, requests and form data provided by the end users or clients of the customer, (b) any data that is programmatically, periodically or automatically received through an integration of the customer, (c) any content stored as a result of processing a configuration data, (d) activity logs used to identify the source of service requests. Actioner deletes any stored usage Data sixty (60) days after the data is produced.
Data archiving and removal policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. Whenever a user account is deleted by a workspace admin, Actioner automatically deletes all data stored within the context of the deleted user account like profile information and the credentials / connections for the third party integrations. Whenever an app is deleted by an app admin, Actioner automatically deletes all data stored within the context of the app like tables, records, workflow, docs, files, etc. Whenever the workspace deletion is initiated by a workspace admin, Actioner automatically deletes all data stored within the context of workspace after a waiting period of 72 hours. After the waiting period, the deletion may take up to 10 days after the termination effective date. When any data is deleted, the archived copy of the data on Actioner’s backup systems will remain for 30 days and the backup data will be securely isolated and protected from any further processing, except as otherwise required by applicable law or regulation.
Data storage policy
At Actioner, ensuring the security of our users' data is paramount. To this end, we employ robust cryptography policies and practices. All data stored within our systems is encrypted at rest using the AES256 encryption standard, providing an additional layer of protection against unauthorized access. Furthermore, we uphold strict encryption standards for data in transit, both within our internal networks and over public channels. All data transmissions utilize TLS1.2 or higher encryption protocols, safeguarding information from interception or tampering. In terms of cryptographic key management, we rely on the AWS Key Management Service (KMS) for secure and controlled handling of cryptographic keys. This includes secure key generation, restricted access, secure storage, regular backups, and periodic rotation of keys. Our integration with AWS services streamlines the encryption process and enhances control over access to keys, thereby bolstering the overall security of our platform.We operate a comprehensive backup program at Actioner. This includes our internal systems, where our backup measures are designed in line with system recovery requirements. With respect to our cloud services, and specifically referring to you and your application data, we also have extensive backup measures in place. Our data backups are retained for 30 days with support for point-in-time recovery and are encrypted using AES-256 encryption.
Data center location(s)
United States
Data hosting details
Actioner is a cloud-native product whose infrastructure is hosted on industry-leading cloud provider Amazon Web Services (AWS). Actioner cloud services and data are hosted on Amazon Web Services (AWS). Where all our computing, messaging, network, and storage layers are located in the US West, our browser application is distributed via our CDN network all over the world. As a design standard, all Actioner services as well as the upstream computing, messaging, network and storage services are running on multiple availability zones (AZs) so that the traffic and the data are distributed among them. This design allows us to tolerate zone-specific failures with no downtime. This multi-zone high availability is the first line of defense for geographic and environmental risks and means that services running in multi-AZ deployments should be able to withstand AZ failure.
Data hosting company
Amazon Web Services (AWS)
App/service has sub-processors
Yes
Guidelines for sub-processors
Certifications & compliance
SOC attestation
Privacy policy
GDPR commitment
Data deletion request procedure
Security
Supports Single Sign On (SSO) with the following providers
Google, Slack, Okta
Supports Security Assertion Markup Language (SAML)
No
Has a dedicated security team
Yes
Contact for security issues
Has a vulnerability disclosure program
Yes
Vulnerability disclosure program URL
Vulnerability disclosure program covers Slack app
Yes
Has a bug bounty program
Yes
Bug bounty program URL
Requires third party authorization/connections
No
Third party services used by this app
Uses token rotation
No
Contributors
Actioner
.png){kind=spacer}
