Update index.md to correct the ordered list numbers. (#2685)

# What this PR does

## Which issue(s) this PR fixes

## Checklist

- [ ] Unit, integration, and e2e (if applicable) tests updated
- [ ] Documentation added (or `pr:no public docs` PR label added if not
required)
- [ ] `CHANGELOG.md` updated (or `pr:no changelog` PR label added if not
required)
This commit is contained in:
Wei-Chin Call 2023-07-30 23:51:48 -07:00 committed by GitHub
parent 6c0488176c
commit 0e37bba24f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -39,13 +39,13 @@ This integration is available for Grafana Cloud OnCall. You must have an Admin r
-d zabbix/zabbix-appliance:latest
```
1. Establish an ssh connection to a Zabbix server.
2. Establish an ssh connection to a Zabbix server.
```bash
docker exec -it zabbix-appliance bash
```
1. Place the [grafana_oncall.sh](#grafana_oncallsh-script) script in the `AlertScriptsPath` directory specified within
3. Place the [grafana_oncall.sh](#grafana_oncallsh-script) script in the `AlertScriptsPath` directory specified within
the Zabbix server configuration file (zabbix_server.conf).
```bash
@ -66,10 +66,10 @@ Within Zabbix web interface, do the following:
1. In a browser, open localhost:80.
1. Navigate to **Adminitstration > Media Types > Create Media Type**.
2. Navigate to **Adminitstration > Media Types > Create Media Type**.
<!--![](../_images/zabbix-1.png)-->
1. Create a Media Type with the following fields.
3. Create a Media Type with the following fields.
- Name: Grafana OnCall
- Type: script
@ -86,13 +86,13 @@ To send alerts to Grafana OnCall, the {ALERT.SEND_TO} value must be set in the [
1. In the web UI, navigate to **Administration > Users** and open the **user properties** form.
1. In the **Media** tab, click **Add** and copy the link from Grafana OnCall in the `Send to` field.
2. In the **Media** tab, click **Add** and copy the link from Grafana OnCall in the `Send to` field.
<!--![](../_images/zabbix-7.png)-->
1. Click **Test** in the last column to send a test alert to Grafana OnCall.
3. Click **Test** in the last column to send a test alert to Grafana OnCall.
<!--![](../_images/zabbix-3.png)-->
1. Specify **Send to** OnCall using the unique integration URL from the above step in the testing window that opens.
4. Specify **Send to** OnCall using the unique integration URL from the above step in the testing window that opens.
Create a test message with a body and optional subject and click **Test**.
<!--![](../_images/zabbix-4.png)
@ -106,11 +106,11 @@ Use the following procedure to configure grouping and auto-resolve.
1. Provide a parameter as an identifier for group differentiation to Grafana OnCall.
1. Append that variable to the subject of the action as `ONCALL_GROUP: ID`, where `ID` is any of the Zabbix [macros](https://www.zabbix.com/documentation/4.2/manual/appendix/macros/supported_by_location).
2. Append that variable to the subject of the action as `ONCALL_GROUP: ID`, where `ID` is any of the Zabbix [macros](https://www.zabbix.com/documentation/4.2/manual/appendix/macros/supported_by_location).
For example, `{EVENT.ID}`. The Grafana OnCall script [grafana_oncall.sh](#grafana_oncallsh-script) extracts this event
and passes the `alert_uid` to Grafana OnCall.
1. To enable auto-resolve within Grafana Oncall, the "Resolved" keyword is required in the **Default subject** field
3. To enable auto-resolve within Grafana Oncall, the "Resolved" keyword is required in the **Default subject** field
in **Recovered operations**.
<!--![](../_images/zabbix-6.png)-->