NSQ Consumer Metrics

Ship your NSQ Consumer Metrics via Telegraf to your Logit.io Stack

Configure Telegraf to ship NSQ Consumer metrics to your Logit.io stacks via Logstash.

Install Integration

Please click on the Install Integration button to configure your stack for this source.

Install Telegraf

This integration allows you to configure a Telegraf agent to send your metrics, in multiple formats, to Logit.io.

Choose the installation method for your operating system:

When you paste the command below into Powershell it will download the Telegraf zip file. Once that is complete, press Enter again and the zip file will be extracted into C:\Program Files\InfluxData\telegraf\telegraf-1.31.2.

wget https://dl.influxdata.com/telegraf/releases/telegraf-1.31.2_windows_amd64.zip -UseBasicParsing -OutFile telegraf-1.31.2_windows_amd64.zip 
Expand-Archive .\telegraf-1.31.2_windows_amd64.zip -DestinationPath 'C:\Program Files\InfluxData\telegraf'

Configure the Telegraf input plugin

The configuration file below is pre-configured to scrape the system metrics from your hosts, add the following code to the configuration file /etc/telegraf/telegraf.conf from the previous step.

# Read metrics from NSQD topic(s)
[[inputs.nsq_consumer]]
  ## Server option still works but is deprecated, we just prepend it to the nsqd array.
  # server = "localhost:4150"
 
  ## An array representing the NSQD TCP HTTP Endpoints
  nsqd = ["localhost:4150"]
 
  ## An array representing the NSQLookupd HTTP Endpoints
  nsqlookupd = ["localhost:4161"]
  topic = "telegraf"
  channel = "consumer"
  max_in_flight = 100
 
  ## Max undelivered messages
  ## This plugin uses tracking metrics, which ensure messages are read to
  ## outputs before acknowledging them to the original broker to ensure data
  ## is not lost. This option sets the maximum messages to read from the
  ## broker that have not been written by an output.
  ##
  ## This value needs to be picked with awareness of the agent's
  ## metric_batch_size value as well. Setting max undelivered messages too high
  ## can result in a constant stream of data batches to the output. While
  ## setting it too low may never flush the broker's messages.
  # max_undelivered_messages = 1000
 
  ## Data format to consume.
  ## Each data format has its own unique set of configuration options, read
  ## more about them here:
  ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
  data_format = "influx"

Read more about how to configure data scraping and configuration options for NSQ Consumer (opens in a new tab)

Configure the output plugin

Once you have generated the configuration file, you need to set up the output plug-in to allow Telegraf to transmit your data to Logit.io in Prometheus format. This can be accomplished by incorporating the following code into your configuration file:

[[outputs.http]]
  url = "https://@metricsUsername:@metricsPassword@@metrics_id-vm.logit.io:@vmAgentPort/api/v1/write"
  data_format = "prometheusremotewrite"
 
  [outputs.http.headers]
    Content-Type = "application/x-protobuf"
    Content-Encoding = "snappy"

Start Telegraf

From the location where Telegraf was installed (C:\Program Files\InfluxData\telegraf\telegraf-1.31.2) run the program providing the chosen configuration file as a parameter:

.\telegraf.exe --config telegraf-demo.conf

Once Telegraf is running you should see output similar to the following, which confirms the inputs, output and basic configuration the application has been started with: Powershell Telegraf information

View your metrics

Data should now have been sent to your Stack.

View My Data

If you don't see take a look at How to diagnose no data in Stack below for how to diagnose common issues.

How to diagnose no data in Stack

If you don't see data appearing in your stack after following this integration, take a look at the troubleshooting guide for steps to diagnose and resolve the problem or contact our support team and we'll be happy to assist.

Telegraf NSQ Consumer Overview

For efficient monitoring and analysis of NSQ Consumer metrics across disparate systems, it's crucial to utilize a powerful and efficient metrics management solution. Telegraf, the open-source server agent designed for collecting and sending telemetry data, is ideally suited for this role. It's capable of capturing NSQ Consumer metrics from a variety of sources, including operational NSQ Consumer instances, databases, and other relevant applications.

Telegraf offers a broad array of input plugins, enabling users to collect metrics from diverse sources such as CPU usage, memory utilization, network traffic, and more - key for understanding NSQ Consumer performance. To store and scrutinize these harvested metrics, organizations can leverage Prometheus, an open-source monitoring and alerting toolkit recognized for its flexible querying language and impressive data visualization capabilities.

To transmit NSQ Consumer metrics from Telegraf to Prometheus, organizations need to configure Telegraf to output metrics in Prometheus format, and then set up Prometheus to scrape these metrics from the Telegraf server. This process involves setting up Telegraf to gather NSQ Consumer metrics, outputting them in the Prometheus format, configuring Prometheus to retrieve these metrics from the Telegraf server, and then visually interpreting the data using Prometheus's dynamic querying and graphical visualization tools.

Upon successful integration of the metrics into Prometheus, further analysis and visualization can be undertaken using Grafana. Grafana, a leading open-source platform known for its monitoring and observability features, is fully compatible with Prometheus. It enables users to construct dynamic, interactive dashboards for a deep-dive into the metrics data, offering a comprehensive understanding of performance trends and potential issues in the NSQ Consumer system.

If you need any further assistance with shipping your log data to Logit.io we're here to help you get started. Feel free to get in contact with our support team by sending us a message via live chat & we'll be happy to assist.

Nginx Metrics NSQ Metrics