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: docs/additional-features/napalm.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# NAPALM
2
2
3
-
NetBox supports integration with the [NAPALM automation](https://napalm-automation.net/) library. NAPALM allows NetBox to serve a proxy for operational data, fetching live data from network devices and returning it to a requester via its REST API. Note that NetBox does not store any NAPALM data locally.
3
+
NetBox supports integration with the [NAPALM automation](https://github.com/napalm-automation/napalm) library. NAPALM allows NetBox to serve a proxy for operational data, fetching live data from network devices and returning it to a requester via its REST API. Note that NetBox does not store any NAPALM data locally.
4
4
5
5
The NetBox UI will display tabs for status, LLDP neighbors, and configuration under the device view if the following conditions are met:
Copy file name to clipboardExpand all lines: docs/additional-features/webhooks.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Webhooks
2
2
3
-
A webhook is a mechanism for conveying to some external system a change that took place in NetBox. For example, you may want to notify a monitoring system whenever the status of a device is updated in NetBox. This can be done by creating a webhook for the device model in NetBox and identifying the webhook receiver. When NetBox detects a change to a device, an HTTP request containing the details of the change and who made it be sent to the specified receiver. Webhooks are configured in the admin UI under Extras > Webhooks.
3
+
A webhook is a mechanism for conveying to some external system a change that took place in NetBox. For example, you may want to notify a monitoring system whenever the status of a device is updated in NetBox. This can be done by creating a webhook for the device model in NetBox and identifying the webhook receiver. When NetBox detects a change to a device, an HTTP request containing the details of the change and who made it be sent to the specified receiver. Webhooks are managed under Logging > Webhooks.
4
4
5
5
!!! warning
6
6
Webhooks support the inclusion of user-submitted code to generate custom headers and payloads, which may pose security risks under certain conditions. Only grant permission to create or modify webhooks to trusted users.
NetBox includes a `housekeeping` management command that should be run nightly. This command handles:
4
+
5
+
* Clearing expired authentication sessions from the database
6
+
* Deleting changelog records older than the configured [retention time](../configuration/optional-settings.md#changelog_retention)
7
+
8
+
This command can be invoked directly, or by using the shell script provided at `/opt/netbox/contrib/netbox-housekeeping.sh`. This script can be copied into your cron scheduler's daily jobs directory (e.g. `/etc/cron.daily`) or referenced directly within the cron configuration file.
9
+
10
+
The `housekeeping` command can also be run manually at any time: Running the command outside of scheduled execution times will not interfere with its operation.
Copy file name to clipboardExpand all lines: docs/configuration/optional-settings.md
+30-22
Original file line number
Diff line number
Diff line change
@@ -52,14 +52,6 @@ BASE_PATH = 'netbox/'
52
52
53
53
---
54
54
55
-
## CACHE_TIMEOUT
56
-
57
-
Default: 0 (disabled)
58
-
59
-
The number of seconds that cached database queries will be retained before expiring.
60
-
61
-
---
62
-
63
55
## CHANGELOG_RETENTION
64
56
65
57
Default: 90
@@ -96,6 +88,22 @@ CORS_ORIGIN_WHITELIST = [
96
88
97
89
---
98
90
91
+
## CUSTOM_VALIDATORS
92
+
93
+
This is a mapping of models to [custom validators](../customization/custom-validation.md) that have been defined locally to enforce custom validation logic. An example is provided below:
94
+
95
+
```python
96
+
CUSTOM_VALIDATORS= {
97
+
'dcim.site': (
98
+
Validator1,
99
+
Validator2,
100
+
Validator3
101
+
)
102
+
}
103
+
```
104
+
105
+
---
106
+
99
107
## DEBUG
100
108
101
109
Default: False
@@ -144,7 +152,7 @@ In order to send email, NetBox needs an email server configured. The following i
144
152
!!! note
145
153
The `USE_SSL` and `USE_TLS` parameters are mutually exclusive.
146
154
147
-
Email is sent from NetBox only for critical events or if configured for [logging](#logging). If you would like to test the email server configuration, Django provides a convenient [send_mail()](https://docs.djangoproject.com/en/stable/topics/email/#send-mail)fuction accessible within the NetBox shell:
155
+
Email is sent from NetBox only for critical events or if configured for [logging](#logging). If you would like to test the email server configuration, Django provides a convenient [send_mail()](https://docs.djangoproject.com/en/stable/topics/email/#send-mail)function accessible within the NetBox shell:
Setting this to False will disable the GraphQL API.
211
+
212
+
---
213
+
198
214
## HTTP_PROXIES
199
215
200
216
Default: None
@@ -271,7 +287,7 @@ Note that enabling this setting causes NetBox to update a user's session in the
271
287
272
288
Default: False
273
289
274
-
Setting this to True will permit only authenticated users to access any part of NetBox. By default, anonymous users are permitted to access most data in NetBox (excluding secrets) but not make any changes.
290
+
Setting this to True will permit only authenticated users to access any part of NetBox. By default, anonymous users are permitted to access most data in NetBox but not make any changes.
275
291
276
292
---
277
293
@@ -327,7 +343,7 @@ Toggle the availability Prometheus-compatible metrics at `/metrics`. See the [Pr
327
343
328
344
## NAPALM_PASSWORD
329
345
330
-
NetBox will use these credentials when authenticating to remote devices via the [NAPALM library](https://napalm-automation.net/), if installed. Both parameters are optional.
346
+
NetBox will use these credentials when authenticating to remote devices via the supported [NAPALM integration](../additional-features/napalm.md), if installed. Both parameters are optional.
331
347
332
348
!!! note
333
349
If SSH public key authentication has been set up on the remote device(s) for the system account under which NetBox runs, these parameters are not needed.
@@ -482,19 +498,11 @@ When remote user authentication is in use, this is the name of the HTTP header w
482
498
483
499
---
484
500
485
-
## RELEASE_CHECK_TIMEOUT
486
-
487
-
Default: 86,400 (24 hours)
488
-
489
-
The number of seconds to retain the latest version that is fetched from the GitHub API before automatically invalidating it and fetching it from the API again. This must be set to at least one hour (3600 seconds).
490
-
491
-
---
492
-
493
501
## RELEASE_CHECK_URL
494
502
495
503
Default: None (disabled)
496
504
497
-
This parameter defines the URL of the repository that will be checked periodically for new NetBox releases. When a new release is detected, a message will be displayed to administrative users on the home page. This can be set to the official repository (`'https://api.github.com/repos/netbox-community/netbox/releases'`) or a custom fork. Set this to `None` to disable automatic update checks.
505
+
This parameter defines the URL of the repository that will be checked for new NetBox releases. When a new release is detected, a message will be displayed to administrative users on the home page. This can be set to the official repository (`'https://api.github.com/repos/netbox-community/netbox/releases'`) or a custom fork. Set this to `None` to disable automatic update checks.
498
506
499
507
!!! note
500
508
The URL provided **must** be compatible with the [GitHub REST API](https://docs.github.com/en/rest).
@@ -505,7 +513,7 @@ This parameter defines the URL of the repository that will be checked periodical
505
513
506
514
Default: `$INSTALL_ROOT/netbox/reports/`
507
515
508
-
The file path to the location where custom reports will be kept. By default, this is the `netbox/reports/` directory within the base NetBox installation path.
516
+
The file path to the location where [custom reports](../customization/reports.md) will be kept. By default, this is the `netbox/reports/` directory within the base NetBox installation path.
509
517
510
518
---
511
519
@@ -521,7 +529,7 @@ The maximum execution time of a background task (such as running a custom script
521
529
522
530
Default: `$INSTALL_ROOT/netbox/scripts/`
523
531
524
-
The file path to the location where custom scripts will be kept. By default, this is the `netbox/scripts/` directory within the base NetBox installation path.
532
+
The file path to the location where [custom scripts](../customization/custom-scripts.md) will be kept. By default, this is the `netbox/scripts/` directory within the base NetBox installation path.
0 commit comments