Processing rules applied to all collectors

Comments

1 comment

  • Official comment
    Avatar
    Brian Goleno

    Hi David, 

    Currently, the best way to do large scale collector management is either via the use of local configuration files, or the use of the Collector Management REST API.  The Processing Rules, and Filters, are not separate resources in our platform, but rather attributes of a Source configuration.  This is something we plan to change over the next year.  I encourage you to add your vote to this Idea:  https://ideas.sumologic.com/ideas/SL-I-1571 .  We use Idea records to track demand, and gather requirements from customers during design. 

    There are currently alternate approaches that are in use by many of our customers. 

    Most of our customers that are managing larger scale deployments are using some sort of automation platform, such as Chef, Puppet, Ansible, or Kubernetes.   These folks use local configuration files, written in JSON, to configure Collectors and Sources.  Details on that process can be found here:  https://help.sumologic.com/Send-Data/Sources/03Use-JSON-to-Configure-Sources .

    Others may choose to modify their collectors or sources using our REST API.  To make it easier to update larger collections of Sources, or upgrade Collectors, we have developed a Collector Management API Client that can be downloaded from our GitHub repo:  https://github.com/SumoLogic/collector-management-client .

     

    Comment actions Permalink

Please sign in to leave a comment.