Skip to content

Commit 6dfcf75

Browse files
Apoorvkudesia-sumologicApoorvkudesia-sumologic
committed
SUMO-251067 | Apoorv | Add. ActiveMQ docs updation
1 parent 1245725 commit 6dfcf75

File tree

1 file changed

+18
-261
lines changed

1 file changed

+18
-261
lines changed

‎docs/integrations/containers-orchestration/activemq.md‎

Lines changed: 18 additions & 261 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,9 @@ This App has been tested with following ActiveMQ versions:
5353

5454
Configuring log and metric collection for the ActiveMQ App includes the following tasks:
5555

56-
### Step 1: Configure Fields in Sumo Logic
57-
58-
Create the following Fields in Sumo Logic prior to configuring collection. This ensures that your logs and metrics are tagged with relevant metadata, which is required by the app dashboards. For information on setting up fields, see [Sumo Logic Fields](/docs/manage/fields).
56+
### Step 1: Fields in Sumo Logic
5957

58+
Following fields will be created as part of app installation process, For information on setting up fields, see [Sumo Logic Fields](https://help.sumologic.com/docs/manage/fields/)
6059
<Tabs
6160
groupId="k8s-nonk8s"
6261
defaultValue="k8s"
@@ -67,7 +66,7 @@ Create the following Fields in Sumo Logic prior to configuring collection. This
6766

6867
<TabItem value="k8s">
6968

70-
If you're using ActiveMQ in a Kubernetes environment, create the fields:
69+
If you're using ActiveMQ in a Kubernetes environment, then these fields will be created:
7170
* `pod_labels_component`
7271
* `pod_labels_environment`
7372
* `pod_labels_messaging_system`
@@ -76,7 +75,7 @@ If you're using ActiveMQ in a Kubernetes environment, create the fields:
7675
</TabItem>
7776
<TabItem value="non-k8s">
7877

79-
If you're using ActiveMQ in a non-Kubernetes environment, create the fields:
78+
If you're using ActiveMQ in a non-Kubernetes environment, then these fields will be created:
8079
* `component`
8180
* `environment`
8281
* `messaging_system`
@@ -270,26 +269,7 @@ This section explains the steps to collect ActiveMQ logs from a Kubernetes envir
270269
```
271270
5. Sumo Logic Kubernetes collection will automatically start collecting logs from the pods having the annotations defined above.
272271

273-
3. **Add an FER to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we need to create a Field Extraction Rule if not already created for Messaging Application Components. To do so:
274-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Logs > Field Extraction Rules**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Logs** select **Field Extraction Rules**. You can also click the **Go To...** menu at the top of the screen and select **Field Extraction Rules**.
275-
2. Click the + Add button on the top right of the table.
276-
3. The **Add Field Extraction Rule** form will appear. Enter the following options:
277-
* **Rule Name**. Enter the name as **App Observability - Messaging**.
278-
* **Applied At.** Choose **Ingest Time**
279-
* **Scope**. Select **Specific Data**
280-
* **Scope**: Enter the following keyword search expression:
281-
```sql
282-
pod_labels_environment=* pod_labels_component=messaging
283-
pod_labels_messaging_system=* pod_labels_messaging_cluster=*
284-
```
285-
* **Parse Expression**. Enter the following parse expression:
286-
```sql
287-
if (!isEmpty(pod_labels_environment), pod_labels_environment, "") as environment
288-
| pod_labels_component as component
289-
| pod_labels_messaging_system as messaging_system
290-
| pod_labels_messaging_cluster as messaging_cluster
291-
```
292-
272+
3. **FERs to normalize the fields in Kubernetes environments**. Labels created in Kubernetes environments automatically are prefixed with `pod_labels`. To normalize these for our app to work, we will have a Field Extraction Rule automatically created for Messaging Application Components named as **App Observability - Messaging**
293273
</TabItem>
294274
<TabItem value="non-k8s">
295275

@@ -455,247 +435,24 @@ At this point, ActiveMQ logs should start flowing into Sumo Logic.
455435
</Tabs>
456436

457437

458-
## Installing ActiveMQ Monitors
459-
460-
This section and below contain instructions for installing Sumo Logic Monitors for ActiveMQ, the app, and descriptions of each of the app dashboards. These instructions assume you have already set up the collection as described in [Collect Logs and Metrics for the ActiveMQ](#collecting-logs-and-metrics-for-activemq).
461-
462-
* To install these alerts, you need to have the Manage Monitors role capability.
463-
* Alerts can be installed by either importing a JSON file or a Terraform script.
438+
## ActiveMQ Monitors
464439

465-
Sumo Logic provides out-of-the-box alerts available through [Sumo Logic monitors](/docs/alerts/monitors) to help you monitor your ActiveMQ clusters. These alerts are built based on metrics and logs datasets and include preset thresholds based on industry best practices and recommendations. For details, see [ActiveMQ Alerts](#activemq-alerts).
466-
467-
:::note
468-
There are limits to how many alerts can be enabled - please see the[ Alerts FAQ](/docs/alerts/monitors/monitor-faq) for details.
469-
:::
440+
import CreateMonitors from '../../reuse/apps/create-monitors.md';
470441

471-
### Method 1: Install the monitors by importing a JSON file:
472-
473-
1. Download the[ JSON file](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/blob/main/monitor_packages/ActiveMQ/activemq.json) that describes the monitors.
474-
2. The[ JSON](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/blob/main/monitor_packages/ActiveMQ/activemq.json) contains the alerts that are based on Sumo Logic searches that do not have any scope filters and therefore will be applicable to all ActiveMQ clusters, the data for which has been collected via the instructions in the previous sections. However, if you would like to restrict these alerts to specific clusters or environments, update the JSON file by replacing the text `messaging_system=activemq` with `<Your Custom Filter>`. Custom filter examples:
475-
* For alerts applicable only to a specific cluster, your custom filter would be: `messaging_cluster=activemq-prod.01`
476-
* For alerts applicable to all clusters that start with `activemq-prod`: `messaging_cluster=activemq-prod*`
477-
* For alerts applicable to a specific cluster within a production environment: `messaging_cluster=activemq-1` and `environment=prod`. This assumes you have set the optional environment tag while configuring collection.
478-
3. Go to Manage Data > Alerts > Monitors.
479-
4. Click **Add**.
480-
5. Click Import and then copy-paste the above JSON to import monitors.
481-
482-
The monitors are disabled by default. Once you have installed the alerts using this method, navigate to the ActiveMQ folder under **Monitors** to configure them. See[ this](/docs/alerts/monitors) document to enable monitors to send notifications to teams or connections. Please see the instructions detailed in Step 4 of this [document](/docs/alerts/monitors/create-monitor).
483-
484-
485-
### Method 2: Install the alerts using a Terraform script
486-
487-
1. Generate an access key and access ID for a user that has the Manage Monitors role capability in Sumo Logic using instructions in [Access Keys](/docs/manage/security/access-keys). To find out which deployment your Sumo Logic account is in, see [Sumo Logic endpoints](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security).
488-
2. [Download and install Terraform 0.13](https://www.terraform.io/downloads.html) or later.
489-
3. Download the Sumo Logic Terraform package for ActiveMQ alerts: The alerts package is available in the Sumo Logic github[ repository](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/tree/main/monitor_packages/ActiveMQ). You can either download it through the “git clone” command or as a zip file.
490-
4. Alert Configuration: After the package has been extracted, navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/ActiveMQ/`.
491-
1. Edit the `activemq.auto.tfvars` file and add the Sumo Logic Access Key, Access Id, and Deployment from Step 1.
492-
```bash
493-
access_id = "<SUMOLOGIC ACCESS ID>"
494-
access_key = "<SUMOLOGIC ACCESS KEY>"
495-
environment = "<SUMOLOGIC DEPLOYMENT>"
496-
```
497-
The Terraform script installs the alerts without any scope filters, if you would like to restrict the alerts to specific clusters or environments, update the variable `'activemq_data_source'`. Custom filter examples:
498-
* A specific cluster `'messaging_cluster=activemq.prod.01'`
499-
* All clusters in an environment `'environment=prod'`
500-
* For alerts applicable to all clusters that start with activemq-prod, your custom filter would be: `'messaging_cluster=activemq-prod*'`
501-
* For alerts applicable to a specific cluster within a production environment, your custom filter would be:`activemq_cluster=activemq-1` and `environment=prod` (This assumes you have set the optional environment tag while configuring collection)
502-
503-
All monitors are disabled by default on installation, if you would like to enable all the monitors, set the parameter monitors_disabled to false in this file.
504-
505-
By default, the monitors are configured in a monitor **folder** called “**ActiveMQ**”, if you would like to change the name of the folder, update the monitor folder name in “folder” key at **activemq.auto.tfvars** file.
506-
507-
5. If you would like the alerts to send email or connection notifications, modify the file **activemq_notifications.auto.tfvars** and populate `connection_notifications` and `email_notifications` as per below examples.
508-
```bash title="Pagerduty Connection Example"
509-
connection_notifications = [
510-
{
511-
connection_type = "PagerDuty",
512-
connection_id = "<CONNECTION_ID>",
513-
payload_override = "{\"service_key\": \"your_pagerduty_api_integration_key\",\"event_type\": \"trigger\",\"description\": \"Alert: Triggered {{TriggerType}} for Monitor {{Name}}\",\"client\": \"Sumo Logic\",\"client_url\": \"{{QueryUrl}}\"}",
514-
run_for_trigger_types = ["Critical", "ResolvedCritical"]
515-
},
516-
{
517-
connection_type = "Webhook",
518-
connection_id = "<CONNECTION_ID>",
519-
payload_override = "",
520-
run_for_trigger_types = ["Critical", "ResolvedCritical"]
521-
}
522-
]
523-
```
524-
525-
Replace `<CONNECTION_ID>` with the connection id of the webhook connection. The webhook connection id can be retrieved by calling the[ Monitors API](https://api.sumologic.com/docs/#operation/listConnections).
526-
527-
For overriding payload for different connection types, see [Set Up Webhook Connections](/docs/alerts/webhook-connections/set-up-webhook-connections).
528-
529-
```bash title="Email Notifications Example"
530-
email_notifications = [
531-
{
532-
connection_type = "Email",
533-
recipients = ["[email protected]"],
534-
subject = "Monitor Alert: {{TriggerType}} on {{Name}}",
535-
time_zone = "PST",
536-
message_body = "Triggered {{TriggerType}} Alert on {{Name}}: {{QueryURL}}",
537-
run_for_trigger_types = ["Critical", "ResolvedCritical"]
538-
}
539-
]
540-
```
442+
<CreateMonitors/>
541443

542-
6. Install the Alerts:
543-
1. Navigate to the package directory `terraform-sumologic-sumo-logic-monitor/monitor_packages/ActiveMQ/` and run `terraform init`. This will initialize Terraform and will download the required components.
544-
2. Run `terraform plan` to view the monitors which will be created/modified by Terraform.
545-
3. Run `terraform apply`.
546-
7. Post Installation: If you haven’t enabled alerts and/or configured notifications through the Terraform procedure outlined above, we highly recommend enabling alerts of interest and configuring each enabled alert to send notifications to other users or services. This is detailed in Step 4 of [this document](/docs/alerts/monitors/create-monitor).
547-
548-
There are limits to how many alerts can be enabled. See the [Alerts FAQ](/docs/alerts/monitors/monitor-faq).
549-
550-
551-
## Installing the ActiveMQ App
552-
553-
Locate and install the app you need from the **App Catalog**. If you want to see a preview of the dashboards included with the app before installing, click **Preview Dashboards**.
554-
555-
1. From the **App Catalog**, search for and select the app.
556-
2. Select the version of the service you're using and click **Add to Library**.
557-
3. To install the app, complete the following fields.
558-
1. **App Name.** You can retain the existing name, or enter a name of your choice for the app.
559-
2. **Data Source.** Choose **Enter a Custom Data Filter** and enter a custom ActiveMQ cluster filter. Examples:
560-
* For all ActiveMQ clusters: `messaging_cluster=*`
561-
* For a specific cluster: `messaging_cluster=activemq.dev.01`.
562-
* Clusters within a specific environment: `messaging_cluster=activemq-1` and `environment=prod` (This assumes you have set the optional environment tag while configuring collection).
563-
4. **Advanced**. Select the **Location in Library** (the default is the Personal folder in the library), or click **New Folder** to add a new folder.
564-
5. Click **Add to Library**.
565-
566-
Once an app is installed, it will appear in your **Personal** folder, or another folder that you specified. From here, you can share it with your organization.
567-
568-
Panels will start to fill automatically. It's important to note that each panel slowly fills with data matching the time range query and received since the panel was created. Results won't immediately be available, but with a bit of time, you'll see full graphs and maps.
569-
570-
571-
## ActiveMQ Alerts
572-
573-
Sumo Logic has provided out-of-the-box alerts available via[ Sumo Logic monitors](/docs/alerts/monitors) to help you quickly determine if the ActiveMQ database cluster is available and performing as expected.
574-
575-
<table>
576-
<tr>
577-
<td>Alert Type (Metrics/Logs) </td>
578-
<td>Alert Name </td>
579-
<td>Alert Description </td>
580-
<td>Trigger Type (Critical / Warning) </td>
581-
<td>Alert Condition </td>
582-
<td>Recover Condition </td>
583-
</tr>
584-
<tr>
585-
<td>Metrics </td>
586-
<td>ActiveMQ - High CPU Usage </td>
587-
<td>This alert fires when CPU usage on a node in a ActiveMQ cluster is high. </td>
588-
<td>Critical </td>
589-
<td> &#62; &#61; 80 </td>
590-
<td> &#60; 80 </td>
591-
</tr>
592-
<tr>
593-
<td>Metrics </td>
594-
<td>ActiveMQ - High Host Disk Usage </td>
595-
<td>This alert fires when there is high disk usage on a node in an ActiveMQ cluster. </td>
596-
<td>Critical </td>
597-
<td>&#62; &#61; 80 </td>
598-
<td>&#60; 80 </td>
599-
</tr>
600-
<tr>
601-
<td>Metrics </td>
602-
<td>ActiveMQ - High Memory Usage </td>
603-
<td>This alert fires when memory usage on a node in an ActiveMQ cluster is high. </td>
604-
<td>Critical </td>
605-
<td>&#62; &#61; 80 </td>
606-
<td>&#60; 80 </td>
607-
</tr>
608-
<tr>
609-
<td>Metrics </td>
610-
<td>ActiveMQ - High Number of File Descriptors in use. </td>
611-
<td>This alert fires when the percentage of file descriptors used by a node in an ActiveMQ cluster is high. </td>
612-
<td>Critical </td>
613-
<td>&#62; &#61; 80 </td>
614-
<td>&#60; 80 </td>
615-
</tr>
616-
<tr>
617-
<td>Metrics </td>
618-
<td>ActiveMQ - High Storage Used </td>
619-
<td>This alert fires when there is storage usage on a node that is high in an ActiveMQ cluster. </td>
620-
<td>Critical </td>
621-
<td>&#62; &#61; 80 </td>
622-
<td>&#60; 80 </td>
623-
</tr>
624-
<tr>
625-
<td>Metrics </td>
626-
<td>ActiveMQ - High Temp Usage </td>
627-
<td>This alert fires when there is high temp usage on a node in an ActiveMQ cluster. </td>
628-
<td>Critical </td>
629-
<td>&#62; &#61; 80 </td>
630-
<td>&#60; 80 </td>
631-
</tr>
632-
<tr>
633-
<td>Logs </td>
634-
<td>ActiveMQ - Maximum Connection </td>
635-
<td>This alert fires when one node in ActiveMQ cluster exceeds the maximum allowed client connection limit. </td>
636-
<td>Critical </td>
637-
<td>&#62; &#61; 1 </td>
638-
<td>&#60; 1 </td>
639-
</tr>
640-
<tr>
641-
<td>Metrics </td>
642-
<td>ActiveMQ - No Consumers on Queues </td>
643-
<td>This alert fires when an ActiveMQ queue has no consumers. </td>
644-
<td>Critical </td>
645-
<td>&#60; 1 </td>
646-
<td>&#62; &#61; 1 </td>
647-
</tr>
648-
<tr>
649-
<td>Metrics </td>
650-
<td>ActiveMQ - No Consumers on Topics </td>
651-
<td>This alert fires when an ActiveMQ topic has no consumers. </td>
652-
<td>Critical </td>
653-
<td>&#60; 1 </td>
654-
<td>&#62; &#61; 1 </td>
655-
</tr>
656-
<tr>
657-
<td>Logs </td>
658-
<td>ActiveMQ - Node Down </td>
659-
<td>This alert fires when a node in the ActiveMQ cluster is down. </td>
660-
<td>Critical </td>
661-
<td>&#62; &#61; 1 </td>
662-
<td>&#60; 1 </td>
663-
</tr>
664-
<tr>
665-
<td>Metrics </td>
666-
<td>ActiveMQ - Too Many Connections </td>
667-
<td>This alert fires when there are too many connections to a node in an ActiveMQ cluster. </td>
668-
<td>Critical </td>
669-
<td>&#62; &#61; 1000 </td>
670-
<td>&#60; 1000 </td>
671-
</tr>
672-
<tr>
673-
<td>Metrics </td>
674-
<td>ActiveMQ - Too Many Expired Messages on Queues </td>
675-
<td>This alert fires when there are too many expired messages on a queue in an ActiveMQ cluster. </td>
676-
<td>Critical </td>
677-
<td>&#62; &#61; 1000 </td>
678-
<td>&#60; 1000 </td>
679-
</tr>
680-
<tr>
681-
<td>Metrics </td>
682-
<td>ActiveMQ - Too Many Expired Messages on Topics </td>
683-
<td>This alert fires when there are too many expired messages on a topic in an ActiveMQ cluster. </td>
684-
<td>Critical </td>
685-
<td>&#62; &#61; 1000 </td>
686-
<td>&#60; 1000 </td>
687-
</tr>
688-
<tr>
689-
<td>Metrics </td>
690-
<td>ActiveMQ - Too Many Unacknowledged Messages </td>
691-
<td>This alert fires when there are too many unacknowledged messages on a node in an ActiveMQ cluster. </td>
692-
<td>Critical </td>
693-
<td>&#62; &#61; 1000 </td>
694-
<td>&#60; 1000 </td>
695-
</tr>
696-
</table>
697444

445+
### ActiveMQ alerts
698446

447+
| Alert Name | Alert Description and conditions | Alert Condition | Recover Condition |
448+
|:--|:--|:--|:--|
449+
| `ActiveMQ - High CPU Usage Alert` | This alert gets triggered when CPU usage on a node in a ActiveMQ cluster is high. | Count >= 80 | Count < 80 |
450+
| `ActiveMQ - High Memory Usage Alert` | This alert gets triggered when memory usage on a node in a ActiveMQ cluster is high. | Count >= 80 | Count < 80 |
451+
| `ActiveMQ - High Storage Used Alert` | This alert gets triggered when there is high store usage on a node in a ActiveMQ cluster. | Count >= 80 | Count < 80 |
452+
| `ActiveMQ - Maximum Connection Alert` | This alert gets triggered when one node in ActiveMQ cluster exceeds the maximum allowed client connection limit. | Count >= 1 | Count < 1 |
453+
| `ActiveMQ - No Consumers on Queues Alert` | This alert gets triggered when a ActiveMQ queue has no consumers. | Count < 1 | Count >= 1 |
454+
| `ActiveMQ - Node Down Alert` | This alert gets triggered when a node in the ActiveMQ cluster is down. | Count >= 1 | Count < 1 |
455+
| `ActiveMQ - Too Many Connections Alert` | This alert gets triggered when there are too many connections to a node in a ActiveMQ cluster. | Count >= 1000 | Count < 1000 |
699456

700457
## Viewing the ActiveMQ Dashboards
701458

0 commit comments

Comments
 (0)