|
| 1 | +--- |
| 2 | +title: Amazon SimpleWorkFlow integration |
| 3 | +tags: |
| 4 | + - Integrations |
| 5 | + - Amazon integrations |
| 6 | + - AWS integrations list |
| 7 | +metaDescription: "New Relic's Amazon SimpleWorkFlow integration: what data it reports and how to enable it." |
| 8 | +--- |
| 9 | + |
| 10 | +[New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for AWS SimpleWorkFlow, sending its metrics data to New Relic. |
| 11 | + |
| 12 | +This document explains the integration's features, how to activate it, and what data can be reported. |
| 13 | + |
| 14 | +## Features |
| 15 | + |
| 16 | +Use our integration to collect and send telemetry data to New Relic from your [Amazon Simple Workflow Service](https://aws.amazon.com/swf/). You can monitor your services, query incoming data, and build dashboards to observe everything at a glance. |
| 17 | + |
| 18 | +## Get started |
| 19 | + |
| 20 | +To enable this integration, see [how to connect AWS services to New Relic](/docs/infrastructure/amazon-integrations/connect/aws-metric-stream-setup/). |
| 21 | + |
| 22 | +Once the integration is set up, you can find your metric data by going to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Metrics and events** and filter by `aws.SimpleWorkFlow`. |
| 23 | + |
| 24 | +## Metric data [#metrics] |
| 25 | + |
| 26 | +This New Relic infrastructure integration collects the following Amazon SWF data: |
| 27 | + |
| 28 | +### SWF metric data |
| 29 | + |
| 30 | +<table> |
| 31 | + <thead> |
| 32 | + <tr> |
| 33 | + <th style={{ width: "200px" }}> |
| 34 | + Metric (min, max, average, count, sum) |
| 35 | + </th> |
| 36 | + <th> |
| 37 | + Unit |
| 38 | + </th> |
| 39 | + <th> |
| 40 | + Description |
| 41 | + </th> |
| 42 | + </tr> |
| 43 | + </thead> |
| 44 | + <tbody> |
| 45 | + <tr> |
| 46 | + <td> |
| 47 | + `DecisionTaskScheduleToStartTime` |
| 48 | + </td> |
| 49 | + <td> |
| 50 | + Time |
| 51 | + </td> |
| 52 | + <td> |
| 53 | + The time interval, in milliseconds, between the time that the decision task was scheduled and when it was picked up by a worker and started. |
| 54 | + </td> |
| 55 | + </tr> |
| 56 | + <tr> |
| 57 | + <td> |
| 58 | + `DecisionTaskStartToCloseTime` |
| 59 | + </td> |
| 60 | + <td> |
| 61 | + Time |
| 62 | + </td> |
| 63 | + <td> |
| 64 | + The time interval, in milliseconds, between the time that the decision task was started and when it closed. |
| 65 | + </td> |
| 66 | + </tr> |
| 67 | + <tr> |
| 68 | + <td> |
| 69 | + `DecisionTasksCompleted` |
| 70 | + </td> |
| 71 | + <td> |
| 72 | + Count |
| 73 | + </td> |
| 74 | + <td> |
| 75 | + The count of decision tasks that have been completed. |
| 76 | + </td> |
| 77 | + </tr> |
| 78 | + <tr> |
| 79 | + <td> |
| 80 | + `PendingTasks` |
| 81 | + </td> |
| 82 | + <td> |
| 83 | + Count |
| 84 | + </td> |
| 85 | + <td> |
| 86 | + The count of pending tasks in a 1 minute interval for a specific Task List. |
| 87 | + </td> |
| 88 | + </tr> |
| 89 | + <tr> |
| 90 | + <td> |
| 91 | + `StartedDecisionTasksTimedOutOnClose` |
| 92 | + </td> |
| 93 | + <td> |
| 94 | + Count |
| 95 | + </td> |
| 96 | + <td> |
| 97 | + The count of decision tasks that started but timed out on closing. |
| 98 | + </td> |
| 99 | + </tr> |
| 100 | + <tr> |
| 101 | + <td> |
| 102 | + `WorkflowStartToCloseTime` |
| 103 | + </td> |
| 104 | + <td> |
| 105 | + Time |
| 106 | + </td> |
| 107 | + <td> |
| 108 | + The time, in milliseconds, between the time the workflow started and when it closed. |
| 109 | + </td> |
| 110 | + </tr> |
| 111 | + <tr> |
| 112 | + <td> |
| 113 | + `WorkflowsCanceled` |
| 114 | + </td> |
| 115 | + <td> |
| 116 | + Count |
| 117 | + </td> |
| 118 | + <td> |
| 119 | + The count of workflows that were canceled. |
| 120 | + </td> |
| 121 | + </tr> |
| 122 | + <tr> |
| 123 | + <td> |
| 124 | + `WorkflowsCompleted` |
| 125 | + </td> |
| 126 | + <td> |
| 127 | + Count |
| 128 | + </td> |
| 129 | + <td> |
| 130 | + The count of workflows that completed. |
| 131 | + </td> |
| 132 | + </tr> |
| 133 | + <tr> |
| 134 | + <td> |
| 135 | + `WorkflowsContinuedAsNew` |
| 136 | + </td> |
| 137 | + <td> |
| 138 | + Count |
| 139 | + </td> |
| 140 | + <td> |
| 141 | + The count of workflows that continued as new. |
| 142 | + </td> |
| 143 | + </tr> |
| 144 | + <tr> |
| 145 | + <td> |
| 146 | + `WorkflowsFailed` |
| 147 | + </td> |
| 148 | + <td> |
| 149 | + Count |
| 150 | + </td> |
| 151 | + <td> |
| 152 | + The count of workflows that failed. |
| 153 | + </td> |
| 154 | + </tr> |
| 155 | + <tr> |
| 156 | + <td> |
| 157 | + `WorkflowsTerminated` |
| 158 | + </td> |
| 159 | + <td> |
| 160 | + Count |
| 161 | + </td> |
| 162 | + <td> |
| 163 | + The count of workflows that were terminated. |
| 164 | + </td> |
| 165 | + </tr> |
| 166 | + <tr> |
| 167 | + <td> |
| 168 | + `WorkflowsTimedOut` |
| 169 | + </td> |
| 170 | + <td> |
| 171 | + Count |
| 172 | + </td> |
| 173 | + <td> |
| 174 | + The count of workflows that timed out, for any reason. |
| 175 | + </td> |
| 176 | + </tr> |
| 177 | + </tbody> |
| 178 | +</table> |
| 179 | + |
| 180 | +All imported data has one dimension: `Domain` |
| 181 | + |
| 182 | +### Create alerts |
| 183 | + |
| 184 | +You can set up alerts to notify you if there are any changes. For example, you can set up an alert to notify relevant parties of critical or fatal errors. |
| 185 | + |
| 186 | +Learn more about [creating alerts here](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/your-first-nrql-condition/). |
0 commit comments