nms
Here are 73 public repositories matching this topic...
-
Updated
May 3, 2020 - Python
-
Updated
Sep 4, 2019 - Shell
-
Updated
Dec 2, 2017 - Python
Is your feature request related to a problem? Please describe.
The NAV documentation does not contain a sufficiently detailed usage guide for configuring threshold rules.
Although the threshold rule editor seems like it is intuitive, with links from several parts of the NAV UI to add new threshold rules, it is not obvious that wildcards are supported in metric paths (Graphite specific). Us
-
Updated
Nov 16, 2019 - Python
-
Updated
May 21, 2020 - C++
-
Updated
Sep 1, 2016 - Java
We need to get Azure build and release pipelines working so deploys to our repo can work. Then, things like Glowstone can depend on Linkstone (GlowstoneMC/Glowstone#952)
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/67803434-port-to-azure-pipelines?utm_campaign=plugin&utm_content=tracker%2F42219367&utm
-
Updated
May 30, 2020 - Java
-
Updated
Aug 29, 2018 - Kotlin
-
Updated
Jul 23, 2017 - Java
-
Updated
Feb 27, 2020 - Java
-
Updated
Jun 3, 2020 - Kotlin
-
Updated
May 10, 2018 - Python
-
Updated
Nov 22, 2019 - Jupyter Notebook
-
Updated
Sep 21, 2018 - C++
-
Updated
Jun 5, 2020 - Python
-
Updated
Jun 11, 2019 - Python
-
Updated
May 30, 2020 - Python
-
Updated
Nov 2, 2018 - Jupyter Notebook
Improve this page
Add a description, image, and links to the nms topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the nms topic, visit your repo's landing page and select "manage topics."
Although Config::Root is correctly set to
$OXIDIZED_HOMEwhen it exists, the config file is not read from this location. Oxidized will only find a config in either/etc/oxidized/configor$HOME/.config/oxidized/config(which I believe is due to Asetus only looking in those locations).Expected behavior is that setting
OXIDIZED_HOMEwould cause the confi