accelo config alerts notifications
Configuring Alert Notifications
The following command configures default alert notifications for Acceldata Pulse.
Before executing, verify if this command is compatible to the targeted Pulse version.
accelo config alerts notificationsOn entering the above command, the following inputs are required from you:
Enter the Joda Timezone value (Example: Asia/Jakarta): :To find your Joda time zone value, see Joda Time.
? Select the metric groups you would like to enable: [Use arrows to move, space to select, type to filter][] druid[] memsql[] nifi[] ntpd[] anomaly[] chrony[] customApp? Select the notifications you would like to enable: [Use arrows to move, space to select, type to filter][] slack[] pagerduty[] hangouts[] webhook[] fileLog[] email[] action[] opsgenie[] line[] telegram[] servicenow[] quantum[] xmatters[] Bigpanda[] Microsoft TeamsServiceNow Notifications
Enter ServiceNow MaxServiceNowMessageThreshold: <default value = 1>Enter ServiceNow DefaultSnoozeIntervalInSecs: <default value = 0>Enter ServiceNow Table Names (comma separated list): : <Enter the Table Names obtained from ServiceNow>Enter ServiceNow BearerToken: : <Enter the BearerToken obtained from ServiceNow>Enter ServiceNow URL: : <Enter the URL obtained from ServiceNow>Enter ServiceNow Caller: : <Enter the Caller ID obtained from ServiceNow>Line Notifications
Enter Line MaxLineMessageThreshold: <default value = 1>✔ Enter Line DefaultSnoozeIntervalInSecs: <default value = 0>✔ Enter Line API Keys (comma separated list): <Enter the API Keys obtained from Line>Telegram Notifications
Enter Telegram MaxTelegramMessageThreshold: <default value = 1>Enter Telegram DefaultSnoozeIntervalInSecs: <default value = 0>Enter Telegram DefaultBotToken: <Enter the default BotToken obtained from Telegram>Enter Telegram DefaultChatIds (comma separated list): <Enter the default ChatIds obtained from Telegram>Jira Notifications
Enter Jira MaxJiraMessageThreshold: <default value = 1>Enter Jira DefaultSnoozeIntervalInSecs: <default value = 0>Enter Jira Issue Type: <one of the three issue types"Bug", "Story", "Task">Enter Jira URL:<Enter the URL obtained from Jira> Enter Jira Project Key: < Enter the project key> Enter Jira Username: <Enter the user name>Enter Jira Token:<Enter the Jira token of the user>Enter Jira Priority:<Enter Jira priority>Enter Jira Label (comma separated list):<Enter the label>Opsgenie Notifications
To set up Opsgenie notifications, assign a value to following parameters after executing the config alerts notifications command.
Enter Opegenie MaxMessageThreshold: <default value = 1>Enter Opsgenie DefaultSnoozeIntervalInSecs: <default value = 0>Enter the Opsgenie API KEY: <Enter the API key obtained from Opsgenie>Email Notifications
To set up email notifications, assign a value to the following parameters after executing the config alerts notifications command.
Enter Email DefaultToEmailIds (comma separated list): <Enter email addresses separated by commas>Enter Email DefaultSnoozeIntervalInSecs: <default value = 0>Enter Email MaxEmailThreshold: <default value = 1>Quantum Notifications
To set up Quantum notifications, assign a value to the following parameters after executing the config alerts notifications command.
INFO: Configuring Quantum Notifications✔ Enter Quantum MaxQuantumMessageThreshold: : 1█Enter Quantum DefaultSnoozeIntervalInSecs: : 0Enter Quantum URL: : dddEnter Quantum Subscription Key: : dddDefault Quantum Ticket Type is: Reporting an OutageDefault Quantum Ticket State is: QueueDefault Quantum App or Platform type is: PulseEnter Quantum ReportedBy [Single emailId]: : username@gmail.comEnter Quantum AssignedTo [Single emailId]: : username@gmail.com✓ Done, Alerts Notifications Configuration file generated✓ Done, Alerts Notifications pushed to Pulse DBSample Configuration
quantum: enable: false maxquantummessagethreshold: 1 defaultsnoozeintervalinsecs: 0 url: <quantum-ticking-url> subscriptionkey: "client-specific-quantum-subscription-key" tickettype: Reporting an Outage state: Queue apporplatform: Pulse reportedby: "<email-id-associated-with-all-tickets-by-pulse>" assignedto: "<automatic-assignee-for-tickets-by-pulse>"xMatters Notifications
To set up xMatters notifications, assign a value to the following parameters after executing the accelo config alerts notifications command.
Select the notifications you would like to enable: xmattersINFO: Configuring XMatters Notifications✔ Enter XMatters MaxXMattersMessageThreshold: : 1Enter XMatters DefaultSnoozeIntervalInSecs: : 0Enter XMatters URL: : "<https:x-matterts url>"✔Register/Verify XMatters UserGroup DetailsEnter Group Name: <group1>Enter Group Key: <Key1>Do you want to add another UserGroup [Y/N] : Y Enter Group Name: <group2>Enter Group Key: <Key2>Do you want to add another UserGroup [Y/N] : YEnter Group Name: <group3>Enter Group Key: <Key3>✔These are the UserGroups created. Configure the required groups by selecting them.Enter XMatters Key: : "<x-matterts Key>"Sample Configuration
xmatters: enable: true maxxmattersmessagethreshold: 1 defaultsnoozeintervalinsecs: 0 url: "<https:x-matterts url>" key: "<x-matters Key>" alerttype: ALERT version: alertapi-0.1 xmatters: enable: true maxxmattersmessagethreshold: 1 defaultsnoozeintervalinsecs: 0 url: "<https:x-matterts url>" alerttype: ALERT version: alertapi-0.1 usergroups: - usergroup: TestGroup 1 userkey: "<x-matters Key1>" - usergroup: Test Group 2 userkey: "<x-matters Key2>"- Configurations need to be tailored based on specific user requirements, indicating a need for customization in different deployment environments.
- For utilizing xMatters tickets and notifications, users must supply a valid API key and the xMatters URL during the notification setup process, emphasizing the necessity of having these credentials for the integration to function properly.
Big Panda Notifications
To set up the Big Panda notifications, assign a value to the following parameters after executing the accelo config alerts notifications command.
INFO: Configuring BigPanda NotificationsEnter BigPanda MaxBigPandaMessageThreshold: : 1✔ Enter BigPanda DefaultSnoozeIntervalInSecs (should be 0 or >= 60): : 0Enter BigPanda URL: : "<https: big panda url>:"✔ Enter BigPanda Auth Token: : *****Enter Mnemonic: : BDP✓ Done, Alerts Notifications Configuration file generated✓ Done, Alerts Notifications pushed to Pulse DBIn the configuration, the supported Mnemonic options are BDO and BDP.
This results in a request to BigPanda server:
- The source is always be "Pulse"
- Severity: Pulse severity to BigPanda severity mapping is as follows:
- Critical => P2
- High => P3
- Everything else (
low|medium|info) => P4
Microsoft Teams Notifications
To set up the Microsoft Teams notifications, assign a value to the following parameters after executing the accelo config alerts notifications command.
INFO: Configuring Microsoft Teams NotificationsEnter Microsoft Teams MaxTeamsMessageThreshold: : 1Enter Microsoft Teams DefaultSnoozeIntervalInSecs (should be 0 or >= 60): : 120✔ Enter Microsoft Teams Webhook URL: < Webhook URL >✓ Done, Alerts Notifications Configuration file generated✓ Done, Alerts Notifications pushed to Pulse DBCreate a Microsoft Teams Webhook URL
You can create the webhook URL using one of the following methods:
- Using the Microsoft Teams application: See Create Incoming Webhooks for instructions.
- Using Microsoft Workflows: See Create Incoming Webhooks with Workflows for detailed steps.
You must change it to a user who has permission to read messages in the private channel or authenticate the Flow bot to write to the private channel.
Options for [flags]
Enter the following command and append the below flags:
accelo config alerts notifications [flags]-h, --help help for notifications-l, --load loads the config into the DBSEE ALSO
- accelo config alerts - Configures alerts for Acceldata Pulse