Name – This is an arbitrary name used for storing, choosing something that identifies the source is good way to differentiate between different collectors.In the HTTP section, select “+ Add Instance” and set the following fields.Navigate to Settings-> Data Collection -> Custom Collectors.Use the following steps to setup the HTTP Collector: The additional log transport mechanisms are the main value of the BrokerVM and the ability to configure on premise often times helps in the design of a secure transport to the cloud. BrokerVM is, as it name suggests, a virtual machine that includes several log capture methods such as syslog, Kafka and remote file CSV. The BrokerVM is the companion technology to XDR that allows for increased functionality typically around network architecture and log capture. One benefit of the API is that it can be implemented in 3rd party technologies directly if they provide that type of integration. This typically is going to require someone with a DevOps skillset. The API provides a programmatical way of getting data. The benefit is that there is lot of different features where the XDR Collector can get additional telemetry. There are several features of the XDR Collector but in regards to this use case, it can be used to collect and transmit data to XDR. The XDR Collector can actually be implemented a number of different ways in XDR. It is easy to spin up several collectors in the UI and does not require any additional hardware or software. The HTTP collector is a HTTP listener that resides on the XDR server. For the purpose of this document, we will use the HTTP Collector but the same data could onboarded using any of the methods defined below. There are a variety of ways to ingest data into XDR to make available in the data lake.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |