-
Notifications
You must be signed in to change notification settings - Fork 0
ASB-3754 Add log file integration docs and cleanup integration section #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
02171f6
4ce9db5
b677935
8cf30b4
a0e1cbd
9dcfe09
91e7812
3d3e4c6
3825c41
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,14 @@ | ||
# Setup SMTP notifications | ||
|
||
# Setup SMTP / Email Notifications | ||
|
||
On the Axonops application menu, select `Settings -> Integrations` . | ||
|
||
`Click` on the `SMTP` area. | ||
Click on the `SMTP` area. | ||
|
||
!!! infomy | ||
|
||
[](./0.JPG) | ||
[](imgs/integrations.jpg) | ||
|
||
Fill in the appropriate details. | ||
|
||
[](./email.JPG) | ||
[](imgs/email-2.jpg) | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Send Notifications to Log Files | ||
|
||
Unlike the other integrations, the Log Files Integration is configured by adding the `alert_log` key to your `axon-server.yml`, typically located at `/etc/axonops/axon-server.yml`. | ||
|
||
When `alert_log.enabled` is `true`, logs will be written to `alert_log.path` for consumption by external services like Splunk. | ||
|
||
```yaml | ||
alert_log: | ||
enabled: true | ||
path: /var/log/axonops/axon-server-alert.log | ||
max_size_mb: 50 | ||
max_files: 5 | ||
``` | ||
|
||
`max_size_mb` and `max_files` are used to define how log rotation is handled. | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,31 @@ | ||
# Setup Microsoft Teams notifications | ||
# Setup Microsoft Teams Integration | ||
|
||
## Create Microsoft Teams Webhook | ||
|
||
### Create Microsoft Teams Webhooks | ||
On the Microsoft Teams interface, go to `Connectors`. | ||
|
||
* On the Microsoft Teams interface, go to `Connectors` | ||
<kbd> | ||
 | ||
</kbd> | ||
 | ||
|
||
<hr></hr> | ||
* Click on configure on the `Incoming Webhook` connector | ||
<kbd> | ||
 | ||
</kbd> | ||
`Configure` the `Incoming Webhook` connector. | ||
|
||
<hr></hr> | ||
* Provide a name and select `Create` | ||
<kbd> | ||
 | ||
</kbd> | ||
 | ||
|
||
<hr></hr> | ||
* Copy the url provided to the clipboard | ||
<kbd> | ||
 | ||
</kbd> | ||
Provide a name and select `Create`. | ||
|
||
<hr></hr> | ||
* On the Axonops application menu, select `Settings -> Integrations` | ||
* `Click` on the `Microsoft Teams` area. | ||
 | ||
|
||
 | ||
Copy the url provided to the clipboard. | ||
|
||
* Enter a `name` and copy the url in the `Webhook URL` field and select `Create` | ||
 | ||
 | ||
|
||
## Create the Microsoft Teams Integration on axon-server | ||
|
||
On the AxonOps application menu, select `Settings -> Integrations`. | ||
|
||
Click on the `Microsoft Teams` area. | ||
|
||
 | ||
|
||
Enter a `name`, copy the url in the `Webhook URL` field, and select `Create`. | ||
|
||
 |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,17 +4,18 @@ The functionality is accessible via ***Settings > Integrations*** | |
|
||
The current integrations are: | ||
|
||
* SMTP | ||
* Pagerduty | ||
* Slack | ||
* Microsoft Teams | ||
* ServiceNow | ||
* OpsGennie | ||
* [SMTP / Email](email-integration.md) | ||
* [Pagerduty](pagerduy-integration.md) | ||
* [Slack](slack-integration.md) | ||
* [Microsoft Teams](microsoft-teams-integration.md) | ||
* [ServiceNow](servicenow-integration.md) | ||
* OpsGenie | ||
* Generic webhooks | ||
* [Log file](log-file-integration.md) (configurable through `axon-server.yml`) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Added hyperlinks here. |
||
|
||
!!! infomy | ||
|
||
 | ||
 | ||
|
||
|
||
|
||
|
@@ -34,7 +35,7 @@ The current routing options are: | |
|
||
Each severity (`info, warning, error`) can be routed independently | ||
|
||
 | ||
 | ||
|
||
### Errors per routing mechanism and severity levels | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,8 @@ | ||
# Setup Pagerduty | ||
|
||
# Setup Pagerduty Integration | ||
|
||
### Create Pagerduty Routing Key | ||
|
||
Using these [steps][1]. Please note down the pagerduty ***routing key*** | ||
|
||
[1]: https://support.pagerduty.com/docs/services-and-integrations | ||
Using these [steps](https://support.pagerduty.com/docs/services-and-integrations){target="_blank"}, note the pagerduty `routing key`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Standardizing on using |
||
|
||
|
||
### Insert Pagerduty Routing Key | ||
|
@@ -16,10 +13,9 @@ On the Axonops application menu, select `Settings -> Integrations` . | |
|
||
!!! infomy | ||
|
||
[](./0.JPG) | ||
[](imgs/integrations.png) | ||
|
||
Add the Pagerduty `routing key` from the previous step into the `integration_key` field. | ||
|
||
|
||
|
||
[](./pd.JPG) | ||
[](imgs/pagerduty-2.jpg) | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,19 @@ | ||
Navigate to ***Settings > Integrations*** and click on ***ServiceNow*** | ||
# Setup ServiceNow Integration | ||
|
||
 | ||
## Login to ServiceNow | ||
|
||
Once you have gathered your **instance name**, **username** and **password** from ServiceNow, you can validate the form: | ||
 | ||
Navigate to `Settings -> Integrations` and click on `ServiceNow`. | ||
|
||
 | ||
|
||
> If you want to see the detailed description of a notification, you'll need to add the `description` field from ServiceNow incidents templates. | ||
Gather the `instance name`, `username`, and `password` from ServiceNow to fill out the form: | ||
 | ||
|
||
 | ||
## Update ServiceNow Incident Template | ||
|
||
If you want to see the detailed description of a notification, you'll need to add the `description` field into the ServiceNow incidents templates. | ||
|
||
 | ||
|
||
 | ||
|
||
 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,54 +1,46 @@ | ||
# Setup Slack | ||
|
||
# Setup Slack Integration | ||
|
||
### Create Slack Incoming Webhooks | ||
|
||
* Go to Slack `Application` | ||
* On the side menu click [](../img/addslackapp.png) | ||
* In search box type `Incoming Webhook`s | ||
* From the App directory click `Install` on `Incoming WebHooks App`. | ||
|
||
|
||
!!! infomy | ||
|
||
[](../img/incomingwebhook.gif) | ||
Add the [Incoming WebHooks](https://slack.com/marketplace/A0F7XDUAZ-incoming-webhooks){target="_blank"} app to Slack. | ||
|
||
* `Click` Add Configuration | ||
> Note: Ensure you're on the correct Slack Workspace by using the Workspace indicator on the top left. | ||
|
||
!!! infomy | ||
|
||
[](../img/AddConfigSLACK.png) | ||
|
||
* In `Post to Channel` Box select an option from the `choose a channel` dropdown menu . | ||
In the `Post to Channel` Box, select an option from the `Choose a channel...` dropdown menu. | ||
|
||
* `Click` `Add Incoming WebHooks Integration` | ||
Click `Add Incoming WebHooks Integration`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Rewrote the above section since it seems like things had changed and using a direct link seemed cleaner, since it's always a struggle for me to navigate to Slack Workspace settings. |
||
|
||
!!! infomy | ||
|
||
[](../img/ChannelBoxSLACK.png) | ||
[](imgs/slack-1.png) | ||
|
||
* `Copy` and make a note of the `WebHook URL` that appears in the `Setup Instructions`. | ||
Copy and make a note of the `WebHook URL` that appears in the `Setup Instructions`. | ||
|
||
!!! infomy | ||
|
||
[](../img/SetupInstrucSLACK.png) | ||
[](imgs/slack-2.png) | ||
|
||
|
||
### Creating the Slack integration on axon-server | ||
|
||
On the Axonops application menu, select `Settings -> Integrations` . | ||
|
||
`Click` on the `Slack` area. | ||
Click on the `Slack` area. | ||
|
||
!!! infomy | ||
|
||
[](./0.JPG) | ||
[](imgs/integrations.png) | ||
|
||
|
||
[1]: #create-slack-incoming-webhooks | ||
|
||
Add the `Webhook URL` from the previous step into the `url` field. | ||
|
||
Optionally, set the `Channel` field to send alerts to a channel other than the default channel | ||
that was defined when the WebHooks Integration was added to the Slack Workspace. | ||
|
||
!!! infomy | ||
|
||
[](./slack.JPG) | ||
[](imgs/slack-4.png) | ||
|
||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -203,11 +203,12 @@ nav: | |
|
||
- Notification Integrations: | ||
- Overview : 'integrations/overview.md' | ||
- PagerDuty Integration: 'integrations/pagerduy-integration.md' | ||
- Slack Integration: 'integrations/slack-integration.md' | ||
- PagerDuty: 'integrations/pagerduy-integration.md' | ||
- Slack: 'integrations/slack-integration.md' | ||
- Microsoft Teams: 'integrations/microsoft-teams-integration.md' | ||
- ServiceNow: 'integrations/servicenow-integration.md' | ||
- Email Integration: 'integrations/email-integration.md' | ||
- SMTP / Email: 'integrations/email-integration.md' | ||
- Log Files: 'integrations/log-file-integration.md' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Standardized the heading since Integrations is already at the top-level. |
||
|
||
- How-to: | ||
- Setup Alert Rules: how-to/setup-alert-rules.md | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The main intended change.