An easy next step is to consolidate your AWS Cloudwatch and GCP Stackdriver metrics into Splunk Infrastructure Monitoring for a more complete view of your overall environment. In many cases, the metrics you collect from Prometheus are just one part of your wider infrastructure, services, and applications landscape.
![splunk props conf splunk props conf](http://cdn-ak.f.st-hatena.com/images/fotolife/k/keisukenishida/20130819/20130819213938.png)
The next steps are up to you: Continue to use both Splunk Infrastructure Monitoring and Prometheus, or standardize to the more configurable collectd OSS agent for better resolution and lower latency for your metric data. You’ll also have the benefits of long term data retention and easy user management, enabling your teams to have a consistent view into their applications. With these two configuration updates, your Prometheus data collection will now be mirrored to your Splunk Infrastructure Monitoring account for use with Splunk Infrastructure Monitoring streaming analytics and smart alerting. # Configures the remote write request’s TLS settings. It is mutually exclusive with `bearer_token`. # Sets the `Authorization` header on every remote write request with the bearer token It is mutually exclusive with `bearer_token_file`. # Sets the `Authorization` header on every remote write request with # Sets the `Authorization` header on every remote write request with the # List of remote write relabel configurations. # Timeout for requests to the remote write endpoint. # The URL of the endpoint to send samples to. This could be used to limit which samples are sent. Write relabeling is applied after external labels. Write_relabel_configs is relabeling applied to samples before sending them to the remote endpoint. The documentation below comes from the Prometheus.io site found here. An alternative example config:Īdd to Splunk Infrastructure Monitoring for your Prometheus scrape jobs. If you want something different than the default endpoint of “/write”, you can specify it with “ListenPath”. To do this, you’ll need to specify the port to bind to.
#Splunk props conf update
Configuration Update 1Īdd remote end point using the Splunk Infrastructure Monitoring Metricproxy:Ĭonfigure Prometheus remote storage to send metric data to a proxy.
#Splunk props conf code
And the configuration changes required to Prometheus are minimal: Only three lines of code in two configuration files need updates. We treat it like any other data source and time series. No changes are required on the Splunk Infrastructure Monitoring platform in order to accept Prometheus.
![splunk props conf splunk props conf](https://www.powerconnect.io/wiki/wp-content/uploads/2016/09/PrepareSplunkforSP06-Removesourcetype-img2.png)
Our customers have been asking for direct integration of Prometheus into Splunk Infrastructure Monitoring to help with their metric consolidation efforts. The Prometheus Expression Browser then allows you to view the collected data in graphs – or to create triggered automation events. A central server is required to pull each of the endpoint resources and aggregate them. Prometheus is a good, low-cost way to get started, as long as you have the development resources available for implementation and instrumentation.Ī typical Prometheus environment consists of integrations that scrape your applications for four metric types counters, gauges, summaries, and aggregated histograms.
![splunk props conf splunk props conf](https://www.powerconnect.io/wiki/wp-content/uploads/2016/09/PrepareSplunkforSP06-Removesourcetype-img1-1030x219.png)
Many companies with production cloud environments use the Prometheus open-source project as a part of their monitoring system.