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
# Running contentctl test with a few arguments, before running the command make sure you checkout into the current branch of the pull request. This step only performs unit testing on all the changes against the target-branch. In most cases this target branch will be develop
29
35
# Make sure we check out the PR, even if it actually lives in a fork
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,7 +138,7 @@ Please use the [GitHub Issue Tracker](https://github.com/splunk/security_content
138
138
If you have questions or need support, you can:
139
139
140
140
* Post a question to [Splunk Answers](http://answers.splunk.com)
141
-
* Join the [#security-research](https://splunk-usergroups.slack.com/archives/C1S5BEF38) room in the [Splunk Slack channel](http://splunk-usergroups.slack.com)
141
+
* Join the [#security-research](https://splunkcommunity.slack.com/archives/CDNHXVBGS) channel in the [Splunk Community Slack.](https://splk.it/slack)
Copy file name to clipboardExpand all lines: app_template/default/data/ui/views/feedback.xml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@
6
6
<html>
7
7
<p5>You can contact the Splunk Threat Research team at<a href = "mailto:[email protected]">[email protected]</a> to send us support requests, bug reports, and questions.
8
8
<br>Specify the request type and the title of any related analytic stories, detections analytics where applicable.</br>
9
-
You can also find us on the <b>#es-content-updates</b><a href = "http://splunk-usergroups.slack.com/"> Splunk Usergroups Slack channel.</a></p5>
9
+
You can also find us on the <b>#es-content-updates</b><a href = "https://splk.it/slack/"> Splunk Community Slack channel.</a></p5>
instances_destroyed by "HourOfDay,isWeekend" into cloud_excessive_instances_destroyed_v1
22
21
dist=expon show_density=true'
23
-
how_to_implement: 'You must have Enterprise Security 6.0 or later, if not you will
22
+
how_to_implement: "You must have Enterprise Security 6.0 or later, if not you will
24
23
need to verify that the Machine Learning Toolkit (MLTK) version 4.2 or later is
25
24
installed, along with any required dependencies. Depending on the number of users
26
25
in your environment, you may also need to adjust the value for max_inputs in the
27
26
MLTK settings for the DensityFunction algorithm, then ensure that the search completes
28
27
in a reasonable timeframe. By default, the search builds the model using the past
29
28
30 days of data. You can modify the search window to build the model over a longer
30
29
period of time, which may give you better results. You may also want to periodically
31
-
re-run this search to rebuild the model with the latest data.
32
-
33
-
More information on the algorithm used in the search can be found at `https://docs.splunk.com/Documentation/MLApp/4.2.0/User/Algorithms#DensityFunction`.'
30
+
re-run this search to rebuild the model with the latest data.\nMore information
31
+
on the algorithm used in the search can be found at `https://docs.splunk.com/Documentation/MLApp/4.2.0/User/Algorithms#DensityFunction`."
0 commit comments