File tree 1 file changed +2
-15
lines changed
1 file changed +2
-15
lines changed Original file line number Diff line number Diff line change 1
- ## Monitors
2
-
3
- ``` json
4
- /$$ /$$ /$$ /$$
5
- | $$$ /$$$ |__/ | $$
6
- | $$$$ /$$$$ /$$$$$$ /$$$$$$$ /$$/$$$$$$ /$$$$$$ /$$$$$$
7
- | $$ $$/$$ $$/$$__ $| $$__ $| $|_ $$_/ /$$__ $$/$$__ $$
8
- | $$ $$$| $| $$ \ $| $$ \ $| $$ | $$ | $$ \ $| $$ \__/
9
- | $$\ $ | $| $$ | $| $$ | $| $$ | $$ /$| $$ | $| $$
10
- | $$ \/ | $| $$$$$$| $$ | $| $$ | $$$$| $$$$$$| $$
11
- |__/ |__/\______/|__/ |__|__/ \___/ \______/|__/
12
- ```
1
+ # Monitors
13
2
14
3
The Agave Monitors API provides a familiar paradigm for monitoring the usability and
15
4
accessibility of storage and execution systems you registered with Agave. Similar to
@@ -22,12 +11,10 @@ history of a given monitor is queryable through the API. As with all resources
22
11
in the Agave Platform, a full event model is available so you can subscribe to
23
12
event you care about such as failed checks, restored system availability, and system disablement.
24
13
25
- ### Creating Monitors
14
+ ## Creating Monitors
26
15
27
16
> Create a new default monitor
28
17
29
-
30
-
31
18
``` plaintext
32
19
monitors-addupdate -S storage.example.com
33
20
```
You can’t perform that action at this time.
0 commit comments