Autodiscovery with Dynamic Configuration Launching

• US 20200136908A1
• Filed: 10/30/2018
• Published: 04/30/2020
• Est. Priority Date: 10/30/2018
• Status: Active Grant

• Current Assignee: Elasticsearch Global B.V. (Elastic N.V.)
• Original Assignee: Elasticsearch Global B.V. (Elastic N.V.)
• Inventors: Perez-Aradros Herce, Carlos
• Granted Patent: US 11,424,984 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 43/065 related to network devices

Abstract

Methods and systems for autodiscovery with dynamic configuration are provided. Exemplary methods include: generating a configuration template for a provider, the configuration template including one or more conditions; monitoring for launch of a new event from a provider; based on the monitoring, detecting the new event; determining, for the detected new event, occurrence of at least one condition of the configuration template; and in response to the determining, automatically launching a configuration associated with the new event. New events may be emitted to a common bus by various providers. The provider may be a container-based provider, container orchestration platform, port-based provider, process-based provider, file search provider, or the like. For container providers, an automatically launched configuration can be automatically stopped once the container exits. The method may include determining that a detected new container includes one or more hints for determining a particular configuration to automatically launch.

Claims

1. A computer-implemented method for autodiscovery with dynamic configuration, the computer-implemented method comprising:

generating a configuration template for a provider, the configuration template including one or more conditions;

monitoring for launch of a new event from a provider;

based on the monitoring, detecting the new event;

determining, for the detected new event, occurrence of at least one condition of the configuration template; and

in response to the determining of the occurrence of the at least one condition of the configuration template for the detected new event, automatically launching a configuration associated with the new event.

2. The method of claim 1, wherein the configuration is a module and the launching is an instantiation of the module.

3. The method of claim 2, wherein the module comprises a group of settings for particular tasks.

4. The method of claim 1, wherein the new event is emitted to a common bus by the provider.

5. The method of claim 4, wherein the new event is one of a plurality of events emitted to the common bus by the provider and other providers.

6. The method of claim 1, wherein the provider is a container provider or a container orchestration platform and the new event is a new container.

7. The method of claim 6, wherein the provider is DOCKER or KUBERNETES.

8. The method of claim 1, wherein the provider is a port-based provider, process-based provider, or file search provider.

9. The method of claim 1, further comprising determining that the detected new container included one or more hints.

10. The method of claim 9, wherein the configuration includes container labels or container annotations, wherein the one or more hints are located in the container labels or container annotations.

11. The method of claim 9, wherein, based on the one or more hints, determining a configuration of a module.

12. The method of claim 1, wherein the monitoring includes monitoring container API for signals indicative of the new container.

13. The method of claim 12, further comprising retrieving logs from the new container based on the one or more hints instead of being based on a default retrieval process.

14. The method of claim 9, wherein the one or more hints include a hint on specific ports aspect to use, so as to enable a port scanner, based on the hint, to scan only the specific ports.

15. The method of claim 1, wherein the configuration automatically launched is automatically stopped once the container exits.

16. The method of claim 1, wherein the configuration template includes a variable, the variable being substituted by actual values from the new event that triggered at least one of the one or more conditions.

17. The method of claim 16, further comprising, creating a new configuration by replacing a variable in the configuration template with a container IP address for the new event which triggered the at least one condition.

18. The method of claim 1, further comprising automatically enriching the new event with DOCKER or KUBERNETES metadata.

19. A system comprising:

a processor; and

a memory communicatively coupled to the processor, the memory storing instructions executable by the processor to perform a method, the method comprising;

generating a configuration template for a provider, the configuration template including one or more conditions;

monitoring for launch of a new event from a provider;

based on the monitoring, detecting the new event;

determining, for the detected new event, occurrence of at least one condition of the configuration template; and

in response to the determining of the occurrence of the at least one condition of the configuration template for the detected new event, automatically launching a configuration associated with the new event.

20. A system comprising:

means for generating a configuration template for a provider, the configuration template including one or more conditions;

means for monitoring for launch of a new event from a provider;

means for, based on the monitoring, detecting the new event;

means for, determining, for the detected new event, occurrence of at least one condition of the configuration template; and

means for, in response to the determining of the occurrence of the at least one condition of the configuration template for the detected new event, automatically launching a configuration associated with the new event.