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: CHANGELOG.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,20 @@
1
1
# @dynatrace-oss/dynatrace-mcp-server
2
2
3
-
- Fixed an issue with stateless HTTP server only taking a single connection
4
-
5
3
## Unreleased Changes
6
4
5
+
- Fixed an issue with stateless HTTP server only taking a single connection
6
+
- Added Grail budget tracking with `DT_GRAIL_QUERY_BUDGET_GB` environment variable (default: 1000 GB, setting it to `-1` disables it), as well as warnings and exceeded alerts in `execute_dql` tool responses
7
+
- Enforce Grail budget by throwing an exception when the budget has been exceeded, preventing further DQL query execution
8
+
7
9
## 0.6.0 (Release Candidate 1)
8
10
9
11
- Added metadata output to `execute_dql` tool which includes scanned bytes information, enabling better cost tracking for Dynatrace Grail data access
10
12
- Added next-steps guidance to `get_entity_details` tool to help users discover related metrics, problems, and logs for entities
11
13
- Added telemetry via Dynatrace OpenKit to improve the product with anonymous usage statistics and error information, enhancing product development while respecting user privacy (can be disabled via `DT_MCP_DISABLE_TELEMETRY` environment variable)
12
14
- Added `server.json` configuration and published the MCP server to the official MCP Registry, making it easier for users to discover and install the server
15
+
- Added metadata output which includes Grail scanned bytes (for cost tracking) to `execute_dql`
16
+
- Added next-steps for `get_entity_details` to find out about metrics, problems and logs
17
+
- Added Telemetry via Dynatrace OpenKit to improve the product with anonymous usage statistics and error information (can be disabled via `DT_MCP_DISABLE_TELEMETRY` environment variable)
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,6 +60,17 @@ depend on the volume (GB scanned).
60
60
1. Review your current Dynatrace consumption model and pricing
61
61
2. Understand the cost implications of the specific data you plan to query (logs, events, metrics) - see [Dynatrace Pricing and Rate Card](https://www.dynatrace.com/pricing/)
62
62
3. Start with smaller timeframes (e.g., 12h-24h) and make use of [buckets](https://docs.dynatrace.com/docs/discover-dynatrace/platform/grail/data-model#built-in-grail-buckets) to reduce the cost impact
63
+
4. Set an appropriate `DT_GRAIL_QUERY_BUDGET_GB` environment variable (default: 1000 GB) to control and monitor your Grail query consumption
64
+
65
+
**Grail Budget Tracking:**
66
+
67
+
The MCP server includes built-in budget tracking for Grail queries to help you monitor and control costs:
68
+
69
+
- Set `DT_GRAIL_QUERY_BUDGET_GB` (default: 1000 GB) to define your session budget limit
70
+
- The server tracks bytes scanned across all Grail queries in the current session
71
+
- You'll receive warnings when approaching 80% of your budget
72
+
- Budget exceeded alerts help prevent unexpected high consumption
73
+
- Budget resets when you restart the MCP server session
63
74
64
75
**To understand costs that occured:**
65
76
@@ -321,6 +332,7 @@ You can set up authentication via **Platform Tokens** (recommended) or **OAuth C
-`DT_GRAIL_QUERY_BUDGET_GB` (number, default: 1000) - Budget limit in GB (base 1000) for Grail query bytes scanned per session. The MCP server tracks your Grail usage and warns when approaching or exceeding this limit.
324
336
325
337
**Platform Tokens are recommended** for most use cases as they provide a simpler authentication flow. OAuth Clients should only be used when specific OAuth features are required.
0 commit comments