#124 - create template and example for targets (#125)

* docs: create template and example for targets

* chore: make pr changes

Author: daceynolan

templates/target/targetExample.md

@@ -0,0 +1,75 @@
+# Event Target for Splunk
+
+This event target receives arbitrary [CloudEvents][ce] over HTTP and sends them to a [Splunk HTTP Event Collector][hec]
+in a [JSON format][ce-jsonformat].
+
+## Prerequisites
+
+- HTTP Event Collector Input
+
+## HTTP Event Collector Input
+
+In order to be able to use the TriggerMesh event target for Splunk, and administrator must:
+
+1. Enable the [HTTP Event Collector][hec] data input in the Splunk installation.
+1. Create a token for receiving data over HTTP.
+
+To do so, open the Splunk web console, then navigate to _Settings > Data > Data inputs_.
+
+![Splunk settings](../images/splunk-target/hec-1.png)
+
+In the list of local inputs, click _HTTP Event Collector_.
+
+![Data inputs](../images/splunk-target/hec-2.png)
+
+Click _New token_ in order to generate a new token with custom settings, then take note of the value of that token. The
+default HEC token (`splunk_hec_token`) is also suitable for use with the TriggerMesh event target for Splunk.
+
+![](../images/splunk-target/hec-3.png)
+
+This procedure is described in more details in the Splunk documentation: [Set up and use HTTP Event Collector in Splunk
+Web ][hec].
+
+## Deploying an Instance of the Target
+
+Open the Bridge creation screen and add a target of type `Splunk`.
+
+![Adding a Splunk target](../images/splunk-target/create-bridge-1.png)
+
+In the Target creation form, give a name to the event Target and add the following information:
+
+- **HEC Endpoint**: URL of the HTTP Event Collector (HEC). This URL varies depending on the type of Splunk installation
+  (Enterprise, self-service Cloud, managed Cloud). Only the scheme, hostname, and port (optionally) are evaluated, the
+  URL path is trimmed if present.
+- **HEC Token**: Reference to a [TriggerMesh secret](../guides/secrets.md) containing a token for authenticating requests against
+  the HEC, as described in the previous section.
+- [**Index**][index]: Name of the index to send events to. When undefined, events are sent to the default index defined
+  in the HEC token's configuration.
+
+![Splunk target form](../images/splunk-target/create-bridge-2.png)
+
+After clicking the `Save` button, you will be taken back to the Bridge editor. Proceed to adding the remaining
+components to the Bridge, then submit it.
+
+![Bridge overview](../images/splunk-target/create-bridge-3.png)
+
+A ready status on the main _Bridges_ page indicates that the Splunk target is ready to accept events.
+
+![Bridge status](../images/bridge-status-green.png)
+
+New events should now be visible in the _Search & Reporting_ app inside Splunk.
+
+![Data summary](../images/splunk-target/search-1.png)
+![Data search](../images/splunk-target/search-2.png)
+
+For more information about using Splunk, please refer to the [Splunk documentation][docs].
+
+## Event Types
+
+The Splunk event target can consume events of any type.
+
+[ce]: https://cloudevents.io/
+[ce-jsonformat]: https://github.com/cloudevents/spec/blob/v1.0/json-format.md
+[hec]: https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector
+[index]: https://docs.splunk.com/Documentation/Splunk/latest/Indexer/Aboutindexesandindexers
+[docs]: https://docs.splunk.com/

templates/target/targetTemplate.md

@@ -0,0 +1,37 @@
+# Event Target for **\_\_\_\_**
+
+This event target sends and receives .......
+
+## Prerequisites
+
+- unordered list of prerequisites
+- unordered list of prerequisites
+- unordered list of prerequisites
+
+## This should be about a prerequisites
+
+1. number list of each step for the prerequisite
+2. number list of each step for the prerequisite
+3. number list of each step for the prerequisite
+
+Or if there are no steps, you can add details about each one.
+
+## This should be about a prerequisites
+
+1. number list of each step for the prerequisite
+2. number list of each step for the prerequisite
+3. number list of each step for the prerequisite
+
+Or if there are no steps, you can add details about each one.
+
+## Deploying an Instance of the Target
+
+Open the Bridge creation screen and add a target of type **\_\_**
+
+Continue adding descriptions and steps needed.
+
+## Event Types
+
+Add the event type info here. This should be a single sentence describing the event.
+
+If schemas are available, add link to those schemas for each type.