@mithung/vunet-mcp-server 2.0.8 → 2.1.0

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.
package/DATA_MODELS.md DELETED
@@ -1,467 +0,0 @@
1
- # Vunet Data Models Reference
2
-
3
- This document lists common data models available in Vunet vuSmartMaps tenants. Use these names with the `vunet_query_metric` tool.
4
-
5
- > **Note:** Actual available models depend on your tenant configuration. Use the `vunet_list_data_models` tool to get the curated list programmatically.
6
-
7
- ## Application Performance Monitoring (APM)
8
-
9
- ### Traces & Transactions
10
- - `Trace Map Data` - Individual trace spans with detailed timing, status codes, and attributes
11
- - `Traces Transaction Volume` - Aggregated transaction counts and statistics
12
- - `Application Response Time` - Response time metrics across services
13
- - `Error Rate` - Error tracking and failure analysis
14
- - `Service Dependencies` - Service-to-service relationships
15
- - `Endpoint Performance` - API endpoint metrics
16
-
17
- ### Application Metrics
18
- - `JVM Metrics` - Java Virtual Machine statistics
19
- - `Thread Pool Metrics` - Thread utilization
20
- - `GC Metrics` - Garbage collection performance
21
- - `Hibernate Query Performance` - ORM query performance
22
- - `Cache Hit Ratio` - Cache effectiveness metrics
23
-
24
- ## Infrastructure Monitoring
25
-
26
- ### Kubernetes
27
- - `Kubernetes Pod Metrics` - Pod-level resource usage and health
28
- - `Kubernetes Node Metrics` - Node-level system metrics
29
- - `Kubernetes Deployment Metrics` - Deployment status and scaling
30
- - `Kubernetes Service Metrics` - Service mesh metrics
31
- - `Kubernetes Namespace Metrics` - Namespace-level aggregations
32
- - `Container Metrics` - Container resource consumption
33
- - `Kubernetes Events` - Cluster events and alerts
34
-
35
- ### System Resources
36
- - `CPU Usage` - CPU utilization by host/process
37
- - `Memory Usage` - Memory consumption and availability
38
- - `Disk I/O` - Disk read/write operations
39
- - `Network I/O` - Network traffic metrics
40
- - `File System Usage` - Disk space utilization
41
- - `System Load` - System load averages
42
-
43
- ### Servers
44
- - `Apache Metrics` - Apache web server statistics
45
- - `Nginx Metrics` - Nginx performance metrics
46
- - `Tomcat Metrics` - Tomcat application server metrics
47
- - `IIS Metrics` - Internet Information Services metrics
48
-
49
- ## Database Monitoring
50
-
51
- ### Relational Databases
52
- - `MySQL Performance` - MySQL query performance and connections
53
- - `MySQL Slow Queries` - Slow query analysis
54
- - `PostgreSQL Metrics` - PostgreSQL database metrics
55
- - `Oracle Metrics` - Oracle database performance
56
- - `SQL Server Metrics` - Microsoft SQL Server statistics
57
- - `Database Connection Pool` - Connection pool utilization
58
-
59
- ### NoSQL Databases
60
- - `MongoDB Metrics` - MongoDB performance
61
- - `Redis Metrics` - Redis cache metrics
62
- - `Cassandra Metrics` - Cassandra cluster health
63
- - `Elasticsearch Metrics` - Elasticsearch search performance
64
-
65
- ## Network Monitoring
66
-
67
- - `Network Latency` - Network response times
68
- - `Packet Loss` - Network packet loss statistics
69
- - `Bandwidth Usage` - Network bandwidth consumption
70
- - `TCP Connections` - TCP connection tracking
71
- - `DNS Query Performance` - DNS resolution metrics
72
- - `SSL Certificate Expiry` - Certificate monitoring
73
-
74
- ## Business Metrics
75
-
76
- - `VuBank Metrics` - Custom business metrics (example tenant)
77
- - `Transaction Success Rate` - Business transaction success/failure
78
- - `User Sessions` - User session analytics
79
- - `Revenue Metrics` - Business revenue tracking
80
- - `Conversion Rate` - Conversion funnel metrics
81
- - `Customer Activity` - User engagement metrics
82
-
83
- ## Log Analytics
84
-
85
- - `Application Logs` - Application log aggregations
86
- - `Error Logs` - Error and exception logs
87
- - `Security Logs` - Security event logs
88
- - `Audit Logs` - Audit trail logs
89
- - `Access Logs` - HTTP access logs
90
-
91
- ## Security & Compliance
92
-
93
- - `Security Events` - Security incident tracking
94
- - `Failed Login Attempts` - Authentication failures
95
- - `Privileged Access` - Privileged user activity
96
- - `Vulnerability Scan Results` - Security scan findings
97
- - `Compliance Metrics` - Compliance status metrics
98
-
99
- ## Custom & Integration
100
-
101
- - Custom data models defined in your tenant
102
- - Third-party integration metrics
103
- - Business-specific KPIs
104
-
105
- ---
106
-
107
- ## Query Examples
108
-
109
- ### Get Slow Traces (Last 24 Hours)
110
- ```json
111
- {
112
- "metric_name": "Trace Map Data",
113
- "relative_time": "24h",
114
- "filters": {
115
- "span.duration": ">5000000"
116
- }
117
- }
118
- ```
119
-
120
- ### Kubernetes Pod CPU Usage
121
- ```json
122
- {
123
- "metric_name": "Kubernetes Pod Metrics",
124
- "relative_time": "1h",
125
- "include": "pod_name,cpu_usage,namespace"
126
- }
127
- ```
128
-
129
- ### Database Query Performance
130
- ```json
131
- {
132
- "metric_name": "MySQL Performance",
133
- "relative_time": "30m",
134
- "filters": {
135
- "query_time": ">1000"
136
- }
137
- }
138
- ```
139
-
140
- ### Error Rate by Service
141
- ```json
142
- {
143
- "metric_name": "Error Rate",
144
- "relative_time": "2h",
145
- "filters": {
146
- "service_name": "api-gateway"
147
- }
148
- }
149
- ```
150
-
151
- ---
152
-
153
- ## Discovery Methods
154
-
155
- ### 1. Use MCP Tool (Recommended)
156
- ```
157
- vunet_list_data_models
158
- ```
159
-
160
- ### 2. Ask via Natural Language
161
- ```
162
- "What data models are available?"
163
- "Show me all Kubernetes metrics"
164
- "List APM data models"
165
- ```
166
-
167
- ### 3. Query Specific Categories
168
- ```
169
- "Show infrastructure metrics"
170
- "List database performance models"
171
- "What application metrics can I query?"
172
- ```
173
-
174
- ---
175
-
176
- ## Data Model Naming Conventions
177
-
178
- - **Spaces in Names**: Use exact names with spaces (e.g., `"Trace Map Data"`)
179
- - **Case Sensitive**: Names are case-sensitive
180
- - **Special Characters**: Some models may contain hyphens or underscores
181
- - **Tenant-Specific**: Custom models follow your organization's naming
182
-
183
- ## Need Help?
184
-
185
- - Check your Vunet UI for available data models
186
- - Use `vunet_get_status` to verify connection
187
- - Contact Vunet support for custom model documentation
188
-
189
- ---
190
-
191
- ## Real-World Use Cases
192
-
193
- ### Use Case 1: Root Cause Analysis for Application Failures
194
-
195
- **Scenario:** VuBank fund transfer service failing with HTTP 401/500 errors
196
-
197
- **Data Models Used:**
198
- 1. **Trace Map Data** - Identify service call chains and failure points
199
- 2. **Kubernetes Pod Metrics** - Verify infrastructure health
200
- 3. **Kubernetes Deployment Metrics** - Check deployment status
201
-
202
- **Query Workflow:**
203
-
204
- ```json
205
- // Step 1: Get recent traces for failing service
206
- {
207
- "metric_name": "Trace Map Data",
208
- "relative_time": "1h",
209
- "filters": {
210
- "service.name": "ibmb-ib"
211
- }
212
- }
213
-
214
- // Step 2: Verify backend service health
215
- {
216
- "metric_name": "Kubernetes Pod Metrics",
217
- "relative_time": "1h",
218
- "filters": {
219
- "namespace": "ibmb",
220
- "pod_name": "ibmb-cbs*"
221
- }
222
- }
223
-
224
- // Step 3: Check deployment status
225
- {
226
- "metric_name": "Kubernetes Deployment Metrics",
227
- "relative_time": "1h",
228
- "filters": {
229
- "deployment_name": "ibmb-cbs"
230
- }
231
- }
232
- ```
233
-
234
- **Outcome:** Identified CBS service returning HTTP 404 (missing REST endpoints) while infrastructure was healthy. See [USE_CASE_RCA.md](USE_CASE_RCA.md) for complete analysis.
235
-
236
- ---
237
-
238
- ### Use Case 2: Performance Degradation Analysis
239
-
240
- **Data Models for Performance Investigation:**
241
-
242
- ```json
243
- // Query slow traces
244
- {
245
- "metric_name": "Trace Map Data",
246
- "relative_time": "4h",
247
- "filters": {
248
- "span.duration": ">5000000" // >5 seconds
249
- }
250
- }
251
-
252
- // Check database performance
253
- {
254
- "metric_name": "MySQL Performance",
255
- "relative_time": "4h",
256
- "filters": {
257
- "query_time": ">1000" // >1 second
258
- }
259
- }
260
-
261
- // Verify resource utilization
262
- {
263
- "metric_name": "Kubernetes Pod Metrics",
264
- "relative_time": "4h",
265
- "include": "pod_name,cpu_usage,memory_usage,namespace"
266
- }
267
- ```
268
-
269
- ---
270
-
271
- ### Use Case 3: Service Dependency Mapping
272
-
273
- **Trace Analysis for Microservices:**
274
-
275
- ```json
276
- {
277
- "metric_name": "Trace Map Data",
278
- "relative_time": "24h",
279
- "filters": {
280
- "service.name": "api-gateway"
281
- }
282
- }
283
- ```
284
-
285
- **Insights Gained:**
286
- - Identify all downstream services called
287
- - Measure response times per service
288
- - Detect cascading failures
289
- - Map service-to-service relationships
290
- - Find bottleneck services
291
-
292
- ---
293
-
294
- ### Use Case 4: Error Pattern Detection
295
-
296
- **Query Failed Requests:**
297
-
298
- ```json
299
- // Get HTTP 500 errors
300
- {
301
- "metric_name": "Trace Map Data",
302
- "relative_time": "6h",
303
- "filters": {
304
- "http.status_code": "500"
305
- }
306
- }
307
-
308
- // Get exceptions
309
- {
310
- "metric_name": "Exception Data",
311
- "relative_time": "6h",
312
- "filters": {
313
- "exception.type": "NullPointerException"
314
- }
315
- }
316
-
317
- // Check error rate by service
318
- {
319
- "metric_name": "Error Rate",
320
- "relative_time": "6h",
321
- "filters": {
322
- "service_name": "payment-service"
323
- }
324
- }
325
- ```
326
-
327
- ---
328
-
329
- ## Pro Tips for Effective Queries
330
-
331
- ### 1. Time Range Selection
332
-
333
- **For Real-Time Issues:**
334
- - Use `15m` or `30m` for immediate problems
335
- - Quick feedback loop for troubleshooting
336
-
337
- **For Trend Analysis:**
338
- - Use `24h`, `7d`, or `30d` for patterns
339
- - Identify recurring issues
340
-
341
- **For Historical Investigation:**
342
- - Use absolute timestamps with `start_time` and `end_time`
343
- - Analyze specific incident windows
344
-
345
- ### 2. Filter Best Practices
346
-
347
- **Be Specific:**
348
- ```json
349
- // Good - specific service
350
- {"service.name": "payment-service"}
351
-
352
- // Too broad - all services
353
- {}
354
- ```
355
-
356
- **Combine Filters:**
357
- ```json
358
- {
359
- "filters": {
360
- "service.name": "api-gateway",
361
- "http.status_code": ">=400",
362
- "span.duration": ">3000000"
363
- }
364
- }
365
- ```
366
-
367
- ### 3. Field Selection
368
-
369
- **Include only needed fields:**
370
- ```json
371
- {
372
- "include": "trace_id,service.name,http.status_code,span.duration"
373
- }
374
- ```
375
-
376
- **Benefits:**
377
- - Faster query execution
378
- - Reduced data transfer
379
- - Easier analysis
380
-
381
- ### 4. Pagination for Large Results
382
-
383
- ```json
384
- {
385
- "metric_name": "Trace Map Data",
386
- "relative_time": "24h",
387
- "limit": 100,
388
- "offset": 0
389
- }
390
- ```
391
-
392
- ---
393
-
394
- ## Common Troubleshooting Scenarios
395
-
396
- ### Scenario: "Why is my application slow?"
397
-
398
- **Investigation Steps:**
399
- 1. Query `Trace Map Data` with `span.duration` filter
400
- 2. Check `MySQL Performance` or `PostgreSQL Metrics`
401
- 3. Verify `Kubernetes Pod Metrics` for resource constraints
402
- 4. Review `JVM Metrics` for garbage collection issues
403
-
404
- ### Scenario: "Service is down"
405
-
406
- **Investigation Steps:**
407
- 1. Query `Kubernetes Pod Metrics` - Check pod status
408
- 2. Query `Kubernetes Container Metrics` - Check for crashes
409
- 3. Query `Trace Map Data` - Verify no successful requests
410
- 4. Check `Error Logs` - Review exception details
411
-
412
- ### Scenario: "Intermittent failures"
413
-
414
- **Investigation Steps:**
415
- 1. Query `Trace Map Data` over longer period (6h-24h)
416
- 2. Look for patterns in `http.status_code` distribution
417
- 3. Check `Kubernetes Events` for pod restarts
418
- 4. Review `Network Latency` metrics
419
-
420
- ### Scenario: "Database queries are slow"
421
-
422
- **Investigation Steps:**
423
- 1. Query `MySQL Slow Queries` or equivalent
424
- 2. Check `Database Connection Pool` utilization
425
- 3. Review `Trace Map Data` for database span durations
426
- 4. Verify `Disk I/O` metrics on database host
427
-
428
- ---
429
-
430
- ## Data Model Categories Quick Reference
431
-
432
- ### 🔍 Debugging & Troubleshooting
433
- - Trace Map Data
434
- - Exception Data
435
- - Error Logs
436
- - Application Logs
437
-
438
- ### 📊 Performance Monitoring
439
- - Application Response Time
440
- - MySQL Performance
441
- - JVM Metrics
442
- - CPU Usage
443
- - Memory Usage
444
-
445
- ### 🏗️ Infrastructure Health
446
- - Kubernetes Pod Metrics
447
- - Kubernetes Deployment Metrics
448
- - Kubernetes Node Metrics
449
- - Container Metrics
450
-
451
- ### 🔒 Security & Compliance
452
- - Security Events
453
- - Failed Login Attempts
454
- - Audit Logs
455
- - SSL Certificate Expiry
456
-
457
- ### 💼 Business Metrics
458
- - Transaction Success Rate
459
- - User Sessions
460
- - Conversion Rate
461
- - Custom KPIs
462
-
463
- ---
464
-
465
- **Last Updated:** February 16, 2026
466
- **Package Version:** 2.0.7
467
- **See Also:** [USE_CASE_RCA.md](USE_CASE_RCA.md) - Complete RCA walkthrough
package/QUICKSTART.md DELETED
@@ -1,213 +0,0 @@
1
- # 🚀 Vunet MCP Server - Quick Start Card
2
-
3
- ## Package Name
4
- **`@mithung/vunet-mcp-server`** - v2.0.0
5
-
6
- ---
7
-
8
- ## Install
9
-
10
- ### Global (Recommended - After Publishing)
11
- ```bash
12
- npm install -g @mithung/vunet-mcp-server
13
- ```
14
-
15
- ### From Tarball (Internal Distribution)
16
- ```bash
17
- npm pack
18
- npm install -g vunet-mcp-server-1.0.0.tgz
19
- ```
20
-
21
- ### From Source (Development)
22
- ```bash
23
- npm install
24
- npm link
25
- ```
26
-
27
- ---
28
-
29
- ## Configure
30
-
31
- ### Single Tenant
32
-
33
- Create `.vscode/mcp.json`:
34
-
35
- **Username/Password:**
36
- ```json
37
- {
38
- "mcpServers": {
39
- "vunet": {
40
- "command": "npx",
41
- "args": ["@mithung/vunet-mcp-server"],
42
- "env": {
43
- "VUNET_TENANT_URL": "https://your-tenant.com",
44
- "VUNET_USERNAME": "username",
45
- "VUNET_PASSWORD": "password",
46
- "VUNET_BU_ID": "1",
47
- "VUNET_VERIFY_SSL": "true"
48
- }
49
- }
50
- }
51
- }
52
- ```
53
-
54
- **Bearer Token:**
55
- ```json
56
- {
57
- "mcpServers": {
58
- "vunet": {
59
- "command": "npx",
60
- "args": ["@mithung/vunet-mcp-server"],
61
- "env": {
62
- "VUNET_TENANT_URL": "https://your-tenant.com",
63
- "VUNET_BEARER_TOKEN": "your-token-here",
64
- "VUNET_BU_ID": "1",
65
- "VUNET_VERIFY_SSL": "true"
66
- }
67
- }
68
- }
69
- }
70
- ```
71
-
72
- ### Multiple Tenants
73
-
74
- ```json
75
- {
76
- "mcpServers": {
77
- "vunet-prod": {
78
- "command": "npx",
79
- "args": ["@mithung/vunet-mcp-server"],
80
- "env": { "VUNET_TENANT_URL": "...", ... }
81
- },
82
- "vunet-staging": {
83
- "command": "npx",
84
- "args": ["@mithung/vunet-mcp-server"],
85
- "env": { "VUNET_TENANT_URL": "...", ... }
86
- }
87
- }
88
- }
89
- ```
90
-
91
- ---
92
-
93
- ## Use
94
-
95
- ### In VS Code (GitHub Copilot Chat)
96
-
97
- ```
98
- Show me traces from the last 2 days
99
- ```
100
-
101
- ```
102
- Get Kubernetes metrics for the last 15 minutes
103
- ```
104
-
105
- ```
106
- Create a performance report for slow traces
107
- ```
108
-
109
- ### Multi-Tenant
110
-
111
- ```
112
- @vunet-prod show error rate for last hour
113
- @vunet-staging compare with yesterday
114
- ```
115
-
116
- ---
117
-
118
- ## Publish
119
-
120
- ```bash
121
- # 1. Login
122
- npm login
123
-
124
- # 2. Publish
125
- npm publish --access public
126
-
127
- # 3. Done!
128
- # Team can now: npm install -g @mithung/vunet-mcp-server
129
- ```
130
-
131
- ---
132
-
133
- ## Files Created
134
-
135
- ✅ `package.json` - npm package config
136
- ✅ `index.js` - MCP server
137
- ✅ `README.md` - Full documentation (14KB)
138
- ✅ `SETUP.md` - Quick setup guide
139
- ✅ `CHANGELOG.md` - Version history
140
- ✅ `PUBLISHING.md` - Publishing guide
141
- ✅ `LICENSE` - MIT License
142
- ✅ `config.example.json` - Config template
143
- ✅ `mcp-config.example.json` - Multi-tenant template
144
- ✅ `.npmignore` - Package exclusions
145
-
146
- ---
147
-
148
- ## Environment Variables
149
-
150
- | Variable | Required | Default | Description |
151
- |----------|----------|---------|-------------|
152
- | `VUNET_TENANT_URL` | ✅ | - | Tenant URL |
153
- | `VUNET_USERNAME` | ✅* | - | Username (*or use bearer token) |
154
- | `VUNET_PASSWORD` | ✅* | - | Password (*or use bearer token) |
155
- | `VUNET_BEARER_TOKEN` | ✅* | - | Bearer token (*or use username/password) |
156
- | `VUNET_BU_ID` | ❌ | `1` | Business Unit |
157
- | `VUNET_VERIFY_SSL` | ❌ | `true` | SSL verify |
158
-
159
- ---
160
-
161
- ## MCP Tools
162
-
163
- 1. **`vunet_query_metric`**
164
- - Query any data model
165
- - Flexible time ranges
166
- - Dynamic filters
167
-
168
- 2. **`vunet_get_status`**
169
- - Connection status
170
- - Authentication status
171
- - Session info
172
-
173
- ---
174
-
175
- ## Data Models (80+)
176
-
177
- - Trace Map Data
178
- - Traces Transaction Volume
179
- - Kubernetes Pod Metrics
180
- - Kubernetes Node Metrics
181
- - VuBank Metrics
182
- - ... and 75+ more
183
-
184
- ---
185
-
186
- ## Next Steps
187
-
188
- 1. ✅ **Test Locally** - Already working!
189
- 2. 📦 **Publish npm** - `npm publish`
190
- 3. 👥 **Share Team** - Config template
191
- 4. 📈 **Monitor** - GitHub Issues
192
-
193
- ---
194
-
195
- ## Documentation
196
-
197
- 📖 Full Guide → [README.md](README.md)
198
- ⚙️ Setup → [SETUP.md](SETUP.md)
199
- 📦 Publishing → [PUBLISHING.md](PUBLISHING.md)
200
- 📋 Summary → [PACKAGE_SUMMARY.md](PACKAGE_SUMMARY.md)
201
-
202
- ---
203
-
204
- ## Support
205
-
206
- 🐛 Issues: GitHub Issues
207
- 💬 Docs: README.md
208
- 📧 Email: support@vunetsystems.com
209
-
210
- ---
211
-
212
- **Made with ❤️ by Vunet Systems**
213
- **Powered by Model Context Protocol**