You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+25-21Lines changed: 25 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,23 +2,20 @@
2
2
Orb agent is a component of the NetBox Discovery solution. It provides network discovery and observability capabilities and is developed by NetBox Labs.
3
3
4
4
## Project status
5
-
6
5
The Orb agent project is currently in the Public Preview stage. For details, please see [NetBox Labs Product and Feature Lifecycle](https://docs.netboxlabs.com/product_feature_lifecycle/). We actively welcome feedback to help us identify and prioritize bugs, features, and improvements.
7
6
8
7
## Getting Started
9
-
To run `orb-agent`, first pull the Docker image from [Docker Hub](https://hub.docker.com/r/netboxlabs/orb-agent):
10
-
8
+
To get started with `orb-agent`, first pull the Docker image from [Docker Hub](https://hub.docker.com/r/netboxlabs/orb-agent):
11
9
12
10
```sh
13
11
docker pull netboxlabs/orb-agent:latest
14
12
```
15
13
16
14
## Orb Agent Configuration
17
-
To run, the Orb agent requires a configuration file. This configuration file consists of three main sections: `Config Manager`, `Backends`, and `Policies`.
18
-
15
+
The Orb agent requires a configuration file. This file consists of three main sections: `config_manager`, `backends`, and `policies`.
19
16
20
17
### Config Manager
21
-
The `Config Manager` section specifies how Orb agent should retrieve it's configuration information. The configuration manager is responsible for processing the configuration to retrieve policies and pass them to the appropriate backend.
18
+
The `config_manager` section specifies how Orb agent should retrieve it's configuration information. The configuration manager is responsible for processing the configuration to retrieve policies and pass them to the appropriate backend.
22
19
23
20
```yaml
24
21
orb:
@@ -30,7 +27,7 @@ orb:
30
27
Currently, only the `local` manager is supported, which retrieves policies from the local configuration file passed to the agent.
31
28
32
29
### Backends
33
-
The `Backends` section specifies what Orb agent backends should be enabled. Each Orb agent backend offers specific discovery or observability capabilities and may require specific configuration information.
30
+
The `backends` section specifies what Orb agent backends should be enabled. Each Orb agent backend offers specific discovery or observability capabilities and may require specific configuration information.
34
31
35
32
```yaml
36
33
orb:
@@ -42,38 +39,45 @@ orb:
42
39
Only the `network_discovery` and `device_discovery` backends are currently supported. They do not require any special configuration.
A special `common` subsection under `Backends` defines configuration settings that are shared with all backends. Currently, it supports passing [diode](https://github.com/netboxlabs/diode) server settings to all backends.
42
+
43
+
#### Common
44
+
A special `common` subsection under `backends` defines configuration settings that are shared with all backends. Currently, it supports passing [diode](https://github.com/netboxlabs/diode) server settings to all backends.
47
45
48
46
```yaml
49
47
backends:
50
48
...
51
49
common:
52
-
diode:
53
-
target: grpc://192.168.0.22:8080/diode
54
-
api_key: ${DIODE_API_KEY}
55
-
agent_name: agent01
50
+
diode:
51
+
target: grpc://192.168.0.22:8080/diode
52
+
api_key: ${DIODE_API_KEY}
53
+
agent_name: agent01
56
54
```
57
55
58
-
59
56
### Policies
60
-
The `Policies` section specifies what discovery policies should be passed to each backend. Policies define specific settings for discovery (such as scheduling and default properties) and the scope (targets). Backends can run multiple policies simultaneously, but for each backend all policies must have a unique name. These policies are defined in the `policies` section and are grouped under a subsection for each backend:
57
+
The `policies` section specifies what discovery policies should be passed to each backend. Policies define specific settings for discovery (such as scheduling and default properties) and the scope (targets). Backends can run multiple policies simultaneously, but for each backend all policies must have a unique name. These policies are defined in the `policies` section and are grouped under a subsection for each backend:
61
58
62
59
```yaml
63
60
orb:
64
61
...
65
62
policies:
66
63
device_discovery:
67
64
device_policy_1:
68
-
# see device_discovery section
65
+
# see docs/backends/device_discovery.md
69
66
network_discovery:
70
67
network_policy_1:
71
-
# see network_discovery section
68
+
# see docs/backends/network_discovery.md
72
69
```
73
70
74
-
## Configuration samples
75
-
You can find sample configurations [here](./docs/config_samples.md) of how to configure Orb agent to run network and device discoveries.
71
+
## Running the agent
76
72
77
-
## Required Notice
73
+
To run `orb-agent`, use the following command from the directory where your created your `agent.yaml` file:
78
74
79
-
Copyright NetBox Labs, Inc.
75
+
```sh
76
+
docker run -v $(PWD):/opt/orb/ netboxlabs/orb-agent:latest run -c /opt/orb/agent.yaml
77
+
```
78
+
79
+
### Configuration samples
80
+
You can find complete sample configurations [here](./docs/config_samples.md) of how to configure Orb agent to run network and device discoveries, as well as the relevant `docker run` commands.
0 commit comments