Skip to content

Infrastructure Integration

Configuration

  1. Configure the agent by editing /etc/nutanix/epoch-dd-agent/conf.d/tcp_check.yamlin the collectors. Example:

    init_config:
    
    instances:
      - name: My first service
        host: myhost.example.com
        port: 8080
        timeout: 1
    
        # The (optional) window and threshold parameters allow you to trigger
        # alerts only if the check fails x times within the last y attempts
        # where x is the threshold and y is the window.
        #
        # threshold: 3
        # window: 5
    
        # The (optional) collect_response_time parameter will instruct the
        # check to create a metric 'network.tcp.response_time', tagged with
        # the url, reporting the response time in seconds.
        #
        # collect_response_time: false
    
        # The (optional) skip_event parameter will instruct the check to not
        # create any event to avoid duplicates with a server side service check.
        # This default to False.
        #
        skip_event: true
    
      # - name: My second service
      #   host: 127.0.0.1
      #   port: 80
    
  2. Check and make sure that all yaml files are valid with following command:

    /etc/init.d/epoch-collectors configcheck
    
  3. Restart the Agent using the following command:

    /etc/init.d/epoch-collectors restart
    
  4. Execute the info command to verify that the integration check has passed:

    /etc/init.d/epoch-collectors info
    

Attributes and Datasources

Shared Attributes

There are some attributes that are common across the integrations. The description to the relevant attributes for this integration can be found here: shared attributes

Attributes

For Tcp_check, below attributes can be used in filters and group by operations in analytics within alerts, dashboards, etc.

Datasources

Datasource Available Aggregations Unit Description
network.tcp.response_time avg max min sum second The response time of a given host and TCP port