@oneuptime/cli 14.0.56 → 14.0.58

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +24 -13
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # @oneuptime/cli
2
2
 
3
- Command-line interface for managing OneUptime resources. Supports all MCP-enabled resources with full CRUD operations, named contexts for multiple environments, and flexible output formats.
3
+ Command-line interface for managing OneUptime resources. Supports every MCP-enabled resource (records with full CRUD operations, telemetry with list, create and count), named contexts for multiple environments, and flexible output formats.
4
4
 
5
5
  ## Installation
6
6
 
@@ -87,7 +87,7 @@ oneuptime context delete old-context
87
87
 
88
88
  ### Resource Operations
89
89
 
90
- Every discovered resource supports these subcommands:
90
+ Every resource supports `list`, `create` and `count`. Records (monitors, incidents, teams and the like) also support `get`, `update` and `delete`; telemetry (logs, metrics, spans and the like) does not:
91
91
 
92
92
  | Subcommand | Description |
93
93
  | -------------------------------------- | -------------------------------------------- |
@@ -191,19 +191,30 @@ Output format and list size are not read from this file. Pass `-o` and `--limit`
191
191
 
192
192
  ## Supported Resources
193
193
 
194
- Run `oneuptime resources` to see all available resource types. Resources are auto-discovered from OneUptime models that have MCP enabled. Currently supported:
194
+ Every resource is a command: `oneuptime <resource> <subcommand>`. Resources are discovered from the OneUptime models that have MCP enabled, and `oneuptime resources` lists the ones your version has (`--type database` for records, `--type analytics` for telemetry).
195
195
 
196
- - **Incident** - Manage incidents
197
- - **Alert** - Manage alerts
198
- - **Monitor** - Manage monitors
199
- - **Monitor Status** - Manage monitor statuses
200
- - **Incident State** - Manage incident states
201
- - **Status Page** - Manage status pages
202
- - **On-Call Policy** - Manage on-call duty policies
203
- - **Team** - Manage teams
204
- - **Scheduled Maintenance Event** - Manage scheduled maintenance
196
+ Records take `list`, `get`, `create`, `update`, `delete` and `count`:
205
197
 
206
- As more models are MCP-enabled in OneUptime, they automatically become available in the CLI.
198
+ | Area | Commands |
199
+ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
200
+ | Monitoring | `monitor`, `monitor-status`, `monitor-status-event` |
201
+ | Incidents | `incident`, `incident-state`, `incident-severity`, `incident-state-timeline`, `incident-public-note`, `incident-internal-note`, `incident-alert` |
202
+ | Alerts | `alert`, `alert-state`, `alert-severity`, `alert-state-timeline`, `alert-internal-note` |
203
+ | Status pages | `status-page`, `status-page-announcement` |
204
+ | Scheduled maintenance | `scheduled-maintenance-event`, `scheduled-maintenance-state`, `scheduled-maintenance-state-timeline` |
205
+ | Teams and on-call | `team`, `on-call-policy` |
206
+ | Security | `security-case`, `security-case-note`, `security-detection`, `security-playbook` |
207
+ | Labels | `label` |
208
+
209
+ Telemetry takes `list`, `create` and `count`:
210
+
211
+ | Area | Commands |
212
+ | ---------------- | ------------------------------------------------------------ |
213
+ | Observability | `log`, `metric`, `span`, `exception-instance`, `monitor-log` |
214
+ | Security | `security-event`, `threat-intel-indicator` |
215
+ | Changes and cost | `change-event`, `kubernetes-cost-allocation` |
216
+
217
+ As more models are MCP-enabled in OneUptime, they become available in the CLI as well. The [command reference](https://oneuptime.com/docs/cli/command-reference) describes every command and its options.
207
218
 
208
219
  ## Development
209
220
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@oneuptime/cli",
3
- "version": "14.0.56",
3
+ "version": "14.0.58",
4
4
  "description": "OneUptime CLI - Command-line interface for managing OneUptime resources",
5
5
  "repository": {
6
6
  "type": "git",
@@ -30,7 +30,7 @@
30
30
  "chalk": "^4.1.2",
31
31
  "cli-table3": "^0.6.5",
32
32
  "commander": "^12.1.0",
33
- "Common": "npm:@oneuptime/common@14.0.56",
33
+ "Common": "npm:@oneuptime/common@14.0.58",
34
34
  "ts-node": "^10.9.2"
35
35
  },
36
36
  "devDependencies": {