This repository has been archived by the owner on Oct 11, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Release v0.0.4, upgraded Go to v1.19, upgraded the Splunk Otel Collector to v0.58.0 upgraded project dependencies
- Loading branch information
Showing
5 changed files
with
35 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# HEC Traces Example | ||
|
||
This example showcases how the agent works with Splunk Enterprise and traces. | ||
|
||
The example runs as a Docker Compose deployment. The collector can be configured to send traces to Splunk Enterprise. | ||
|
||
Splunk Enterprise is configured to receive data from the Splunk OpenTelemetry Collector using the HTTP Event Collector. To learn more about HEC, see [Configure the Splunk HTTP Event Collector](https://dev.splunk.com/enterprise/docs/dataapps/httpeventcollector/) for use with additional technologies. | ||
|
||
To deploy the example: | ||
1. Check out the [Splunk OpenTelemetry Collector repository](https://github.com/signalfx/splunk-otel-collector). | ||
2. Open a terminal. | ||
3. Type the following commands: | ||
```bash | ||
$> cd examples/splunk-hec-traces | ||
$> docker-compose up --build | ||
``` | ||
You can stop the example by pressing Ctrl + C. | ||
|
||
Splunk Enterprise becomes available on port 18000. Log in to [http://localhost:18000](http://localhost:18000) with the user name `admin` and password `changeme`. | ||
|
||
Once logged in, visit the [spans comparisons dashboard](http://localhost:18000/en-US/app/search/spans_time_comparisons) to see a comparison of traces over time sent by the Splunk OpenTelemetry Collector. | ||
|
||
You can also search traces for information, such as querying by tag or any element of traces, by searching the traces index `index=traces`. | ||
|
||
![Traces dashboard](traces_comparison_dashboard.png) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters