Commit 17597d30 authored by Jochen Kressin's avatar Jochen Kressin
Browse files

initial structure of Signals docs

parent d3ea5e90
......@@ -80,6 +80,7 @@ labels:
changelogs-searchguard: "Search Guard Changelogs"
changelogs-tlstool: "TLS Tool Changelogs"
resources: Resources
signals: Signals Alerting
7x-36: Search Guard 7.x-36
7x-35: Search Guard 7.x-35
6x-25: Search Guard 6.x-25
......@@ -106,6 +107,7 @@ labels:
docs_elasticstack: Documentation
docs_other_integrations: Documentation
docs_systemintegrators: Documentation
docs_signals: Documentation
troubleshooting: Troubleshooting
changelogs: Changelogs
resources: Resources
......@@ -165,6 +167,9 @@ collections:
docs_systemintegrators:
output: true
permalink: :title
docs_signals:
output: true
permalink: :title
troubleshooting:
output: true
permalink: :title
......
---
title: Actions
html_title: Creating Actions for Signals Alerting
slug: elasticsearch-alerting-actions
category: signals
subcategory: actions
order: 700
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Creating Actions
{: .no_toc}
{% include toc.md %}
---
title: Email Actions
html_title: Creating Email Actions for Signals Alerting
slug: elasticsearch-alerting-actions-email
category: actions
order: 200
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Email Actions
{: .no_toc}
{% include toc.md %}
---
title: Index Actions
html_title: Creating Index Actions for Signals Alerting
slug: elasticsearch-alerting-actions-index
category: actions
order: 100
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Index Actions
{: .no_toc}
{% include toc.md %}
---
title: Pagerduty Actions
html_title: Creating Pagerduty Actions for Signals Alerting
slug: elasticsearch-alerting-actions-pagerduty
category: actions
order: 500
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Pagerduty Actions
{: .no_toc}
{% include toc.md %}
## Coming Soon
\ No newline at end of file
---
title: Slack Actions
html_title: Creating Slack Actions for Signals Alerting
slug: elasticsearch-alerting-actions-slack
category: actions
order: 400
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Slack Actions
{: .no_toc}
{% include toc.md %}
---
title: Webhook Actions
html_title: Creating Webhook Actions for Signals Alerting
slug: elasticsearch-alerting-actions-webhook
category: actions
order: 300
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Webhook Actions
{: .no_toc}
{% include toc.md %}
---
title: Execution chain
html_title: Chaining Inputs, Transformations and Conditions
slug: elasticsearch-alerting-chaining
category: signals
order: 250
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Chaining Inputs, Transformations and Conditions
{: .no_toc}
{% include toc.md %}
---
title: Conditions
html_title: Creating Conditions for Signals Alerting
slug: elasticsearch-alerting-conditions
category: signals
subcategory: conditions
order: 600
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Conditions
{: .no_toc}
{% include toc.md %}
---
title: Script Conditions
html_title: Creating Script Conditions for Signals Alerting
slug: elasticsearch-alerting-conditions-script
category: conditions
order: 100
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Script Conditions
{: .no_toc}
{% include toc.md %}
---
title: Getting started with Signals Alerting
html_title: Getting started with Signals Alerting
slug: elasticsearch-alerting-getting-started
category: signals
order: 100
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Getting started with Signals Alerting for Elasticsearch
{: .no_toc}
{% include toc.md %}
---
title: Inputs
html_title: Creating inputs for Signals Alerting
slug: elasticsearch-alerting-inputs
category: signals
subcategory: inputs
order: 400
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Inputs
{: .no_toc}
Each watch can have one or more inputes. Inputs can be freely defined anywhere in the execution chain.
Each input will fetch data from a data source, and place it in the runtime data context under a configurable key for later usage.
At the moment, Signals supports the following input types:
* Constants
* Define constants you can then use at multiple places in the execution chain
* Elasticsearch
* Use the full power of Elasticsearch queries and aggregations
* HTTP
* Pull in data from a REST endpoint
All data from all inputs can be combined by using [Transformation](transformations_transformations.md) and [Calculations](transformations_calculations.md), used in [Conditions](conditions.md) and pushed to [action endpoints](actions.md).
---
title: Constants
html_title: Creating Constants inputs for Signals Alerting
slug: elasticsearch-alerting-inputs-constants
category: inputs
order: 900
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Creating inputs
{: .no_toc}
{% include toc.md %}
---
title: Elasticsearch
html_title: Creating Elasticsearch inputs for Signals Alerting
slug: elasticsearch-alerting-inputs-elasticsearch
category: inputs
order: 100
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Creating inputs
{: .no_toc}
{% include toc.md %}
---
title: HTTP
html_title: Creating HTTPP inputs for Signals Alerting
slug: elasticsearch-alerting-inputs-http
category: inputs
order: 200
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Creating inputs
{: .no_toc}
{% include toc.md %}
---
title: How Signals Alerting works
html_title: How Signals Alerting works
slug: elasticsearch-alerting-how-it-works
category: signals
order: 200
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Getting started with Signals Alerting for Elasticsearch
{: .no_toc}
{% include toc.md %}
---
title: REST API
html_title: Managing Signals Alerting with the REST API
slug: elasticsearch-alerting-rest-api
category: signals
subcategory: signals-rest
order: 900
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# REST API
{: .no_toc}
{% include toc.md %}
---
title: Delete Destination
html_title: Delete a destination with the REST API
slug: elasticsearch-alerting-rest-api-destination-delete
category: signals-rest
order: 1000
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Delete Destination
{: .no_toc}
{% include toc.md %}
---
title: Get Destination
html_title: Get a destination with the REST API
slug: elasticsearch-alerting-rest-api-destination-get
category: signals-rest
order: 800
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Get Destination
{: .no_toc}
{% include toc.md %}
---
title: Put Destination
html_title: Put a destination with the REST API
slug: elasticsearch-alerting-rest-api-destination-put
category: signals-rest
order: 900
layout: docs
edition: preview
description:
---
<!--- Copyright 2019 floragunn GmbH -->
# Put Destination
{: .no_toc}
{% include toc.md %}
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment