You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/hdinsight/hdinsight-component-versioning.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,32 +34,32 @@ Support is defined as a time period that an HDInsight version is supported by Mi
34
34
Standard support provides updates and support on HDInsight clusters. Microsoft recommends building solutions using the most recent fully supported version.
35
35
36
36
Standard support includes
37
-
- Ability to create support requests on HDInsight 4.0 clusters.
38
-
- Support for troubleshooting solutions built on 4.0 clusters.
37
+
- Ability to create support requests for the cluster.
38
+
- Support for troubleshooting solutions built on the cluster(s).
39
39
- Requests to restart services or nodes.
40
40
- Root cause analysis investigations on support requests.
41
41
- Root cause analysis or fixes to improve job or query performance.
42
42
- Root cause analysis or fixes to improve customer-initiated changes, for example, changing service configurations or issues due to custom script actions.
43
43
- Product updates for critical security fixes until version retirement.
44
44
- Scoped product updates to the HDInsight Resource provider.
45
-
- Selective fixes or changes to HDInsight 4.0 images or open-source software (OSS) component versions.
45
+
- Selective fixes or changes to HDInsight images or open-source software (OSS) component versions.
46
46
47
47
### Basic support
48
48
49
49
Basic support provides limited servicing to the HDInsight Resource provider. HDInsight images and open-source software (OSS) components won't be serviced. Only critical security fixes will be patched on HDInsight clusters.
50
50
51
51
Basic support includes
52
-
- Continued use of existing HDInsight 3.6 clusters.
53
-
- Ability for existing HDInsight 3.6 customers to create new 3.6 clusters.
54
-
- Ability to scale HDInsight 3.6 clusters up and down via autoscale or manual scale.
52
+
- Continued use of existing clusters.
53
+
- Ability for existing HDInsight customers to create new clusters in the same version.
54
+
- Ability to scale clusters up and down via autoscale or manual scale.
55
55
- Scoped product updates to the HDInsight Resource provider.
56
56
- Product updates for critical security fixes until version retirement.
57
-
- Ability to create support requests on HDInsight 3.6 clusters.
57
+
- Ability to create support requests for the cluster.
58
58
- Requests to restart services or nodes.
59
59
60
60
Basic support doesn't include
61
-
- Fixes or changes to HDInsight 3.6 images or open-source software (OSS) component versions.
62
-
- Support for troubleshooting solutions built on 3.6 clusters.
61
+
- Fixes or changes to HDInsight images or open-source software (OSS) component versions.
62
+
- Support for troubleshooting solutions built on the cluster version.
63
63
- Adding new features or functionality.
64
64
- Support for advice or ad-hoc queries.
65
65
- Root cause analysis investigations on support requests.
Copy file name to clipboardExpand all lines: articles/sentinel/connect-cef-ama.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ Before you begin, verify that you have:
63
63
64
64
### Configure a log forwarder
65
65
66
-
To ingest Syslog and CEF logs into Microsoft Sentinel, you need to designate and configure a Linux machine that collects the logs from your devices and forwards them to your Microsoft Sentinel workspace. This machine can be a physical or virtual machine in your on-premises environment, an Azure VM, or a VM in another cloud. This machine must have Azure Arc installed (see the [prerequisites](#prerequisites)).
66
+
To ingest Syslog and CEF logs into Microsoft Sentinel, you need to designate and configure a Linux machine that collects the logs from your devices and forwards them to your Microsoft Sentinel workspace. This machine can be a physical or virtual machine in your on-premises environment, an Azure VM, or a VM in another cloud. If this machine is not an Azure VM, it must have Azure Arc installed (see the [prerequisites](#prerequisites)).
67
67
68
68
This machine has two components that take part in this process:
69
69
@@ -131,7 +131,7 @@ Select the machines on which you want to install the AMA. These machines are VMs
131
131
> On each source machine that sends logs to the forwarder in CEF format, you must edit the Syslog configuration file to remove the facilities that are being used to send CEF messages. This way, the facilities that are sent in CEF won't also be sent in Syslog.
132
132
133
133
1. Select the **Collect** tab and select **Linux syslog** as the data source type.
134
-
1. Configure the minimum log level for each facility. When you select a log level, Microsoft Sentinel collects logs for the selected level and other levels with lower severity. For example, if you select **LOG_ERR**, Microsoft Sentinel collects logs for the **LOG_ERR**, **LOG_WARNING**, **LOG_NOTICE**, **LOG_INFO**, and **LOG_DEBUG** levels.
134
+
1. Configure the minimum log level for each facility. When you select a log level, Microsoft Sentinel collects logs for the selected level and other levels with higher severity. For example, if you select **LOG_ERR**, Microsoft Sentinel collects logs for the **LOG_ERR**, **LOG_CRIT**, **LOG_ALERT**, and **LOG_EMERG** levels.
135
135
136
136
:::image type="content" source="media/connect-cef-ama/dcr-log-levels.png" alt-text="Screenshot showing how to select log levels when setting up the DCR.":::
0 commit comments