- #221 - Generate setup.py file for downloaded python extensions
- #182 - Update contributor's guide
- #154 - Update Strato packages
- #233 - Fix Barista icons URL
- #225 - generated certificates not used when initializing workspace
- #224 - Cannot add tenant by friendly-name alias
- All requests through axios given a higher limit for following redirects
- Prometheus scraping would not read any data
- #218 - null properties in configUi break python extension conversion
- JMX Conversion would not work offline
- Express.js open redirect in malformed urls
- Path traversal in webpack-dev-middleware
- Follow-redirects' proxy-authorization header kept across hosts
- #190 - Converting JMX extension breaks when choosing not to include metrics on Host view
- #184 - Cancellation Token not processed for subprocess commands
- #207 - Error initializing workspace with existing custom extension. "Invalid CEN header"
- #208 - Uploaded extensions can't be downloaded and unpacked on Windows
- #191 - Windows - creating extensions in a different drive doesn't work
- #175 - Dynatrace Log channel is empty
- #178 - Simulator doesn't run second time on remote simulation
- #179 - Configure extension command broken due to simulator.json
- #176 - Bump follow-redirects from 1.15.2 to 1.15.4 in /webview-ui
- #169 - Initialize workspace with python doesn't work when workspace path has spaces
- #170 - Extension simulator UI doesn't open outside of an extension workspace
- #171 - Default configuration for simulations isn't loaded
- #137 - Build command should communicate if not ready to trigger
- #149 - Use simple metric in alerts instead of metric selector
- #152 - Add setting for max number of extension packages kept in dist
- #126 - Load all SNMP MIBs shipped with ActiveGate
- #128 - Logging improvements
- #146 - Cannot build python extension with custom platforms
- #14 - Axios cross-site request forgery vulnerability
- #148 - Python commands use global interpreter instead of virtual environment
- Cannot disable fast development mode
- JMX converts metric unit to "PerSecondPerSecond" in rate metric
- #139 - JMX conversion automation improvements
- Check out the online guide released for this feature
- #132 - Error "cannot read name" when activating new extension
- #135 - Screens rejected on subsequent uploads
- #127 - .DS_Store files may impact zip archiving for Mac users
- #134 - Validation broken from special characters on path
- #133 - Create Alert command fails if no topology exists
- Prometheus scraping from file not working
- Code Actions from Prometheus scraped metrics not being suggested
- Project rebranding to "Dynatrace Extensions", along with new icons
- Documentation moved to Dynatrace Developer Portal
- Migration utility from previous versions of this project
- Hover information for SNMP object IDs and names
- #118 - Support for Platform URLs
- #109 - Prometheus scraping from file
- #117 - Connection checks for Dynatrace environments
- #78 - Attach generated alerts to entities
- #98 - Support for local MIB files in snmp extensions
- #122 - Tighten regexes for tenants and improve no data messaging
- #113 - Temporary file interface closes too early
- #121 - INJECTIONS card gets error diagnostic over extension's name
- #115 - Uninstall/Disable of Copilot disables/uninstalls YAML extension
- Disabling Copilot still requires disabling all other extensions that depend on YAML (issue of VSCode marketplace)
- Uninstalling will only uninstall the Copilot alone
- Guards put in place for parallel running with the newer version of this project (unreleased currently)
- #81 - Monitoring Configurations part 2
- Copilot can now generate configuration files for Extensions that are not deployed yet
- When configuring deployed extensions, can select from files in the
configfolder - Any configuration from the tenant can be saved to the
configfolder of the current workspace - The "scope" of a monitoring configuration offers suggestions from tenant
- #89 - .gitignore as part of workspace initialization
- The WMI Code Lens would not be able to interpret single item responses
- Workspaces initialized since version 1.2.1 may be unaccessible afterwards
- For any such workspace, re-initialize it once the add-on was updated to version 1.2.3
- Overview dashboard not added correctly to yaml
- #103 - SNMP diagnostics highlight all OIDs as unknown
- #94 - When building python extensions, only one extra platform is supported
- #82 - Error message shown when opening VSCode outside of a workspace
- #83 - Prometheus code lens appears too often
- #86 - Extension not bundled correctly
- #87 - Metric table cards not diagnosed correctly
- #85 - Git-based functionality removed
- #64 - Reduce the amount of yaml parsing invocations
- Installation package reduced to ~420KB
- Extension startup times consistent at 100-250 ms
- #75 - Link to configure extension not working on dashboard
- #74 - Create documentation command fails at alert processing
- #72 - Create alert can generate invalid file name
- #76 - Generated dashboard title to include extension name
- #62 - Long running commands can be cancelled
- #65 - WMI Code Lens does not clear correctly
- Feature settings toggle not working for WMI & Screen Code Lens
- #63 - Prometheus cached results clear when switching endpoints
- #67 - Create Alert command prefers metrics from datasource
- #59 - Credentials can now be stored in global settings
- #56 - Build command saves changes to extension manifest before running
- #45 - Diagnostics collection offers insights into SNMP
- #52 - Copilot uses fused credential files
- #29 - Context menus in the Workspaces view allow switching features on/off
- #58 - URLs for environments are now validated more accurately
- #55 - Code lens for Prometheus allow changing endpoint details
- #54 - Code lens for Prometheus displays how many metrics we scraped
- Since this is a live version available on Marketplace it will appear as a new extension. This means any previous version should be removed and any workspaces will have to be initialized again.
- Starting with this version, the add-on only supports fused credential files. If you want to use an older format (key & certificate as separate files) you must paste the contents manually and create a fused file.
- #44 - Credential files should support relative paths
- #23 - Checks and warnings regarding YAML Schema extension
- #49 - Internal repo checks don't cover Python repos
- #48 - Build command breaks if name or version is surrounded by quotes
- Extension automatically installs the required YAML by RedHat extension too
- Extension activates as soon as vscode starts up
- Python building includes both linux & windows modules
- Errors on non-existent commands when extension not in a valid workspace
- #41 - Overview dashboard not adding metrics for sql datasource
- Certificates are not being uploaded to local installations correctly
- Increased logging in DevTools to aid troubleshooting
- Card key diagnostics more accurate
- Workspace structure allows
extension/extension.yamlone level deep as well as in root of the workspace
- #34 - Limit YAML re-formatting for small changes
- #36 - Automatically place certificates in the OA+AG directories
- Command "Upload certificate" has also been renamed to "Distribute certificate" to better indicate this
- #37 - Prometheus Scraper keeps "counter" metric type
- #35 - Credentials generated by the copilot fail validation on component side
- #33 - BYO Certs don't work with the latest dt-cli format bug
- #31 - Building Python extension does not link to upload command
- #26 - WMI Queries utility for the WMI datasource (code lens)
- #28 - WMI Code Actions for auto-completion
- First diagnostics fix actions. Fix one or all your metric key issues.
- Diagnostics for metric keys are more accurately highlighted
- #22 - Wait needed after Deleting Oldest Extension Version
- Fixed for all: Regular Build/Upload + FastMode Build
- Building python extensions uses virtual environment if one is detected (depends on VSCode Python extension)
- #21 - Fast development mode build issues
- #20 - Create documentation is not invoked properly
- Diagnostics for metric keys are more accurate now
- Metrics by featureset are now collected more accurately
- Diagnostics for metric keys
- Screen creation not adding \n after last screen
- Screen generation not building action snippet correctly
- Entity filters snippet not correctly indented when being generated
- Status bar can create Pull Requests for Dynatrace official repositories
- Code Lens for opening the unified analysis screens
- Environment token is obfuscated during setup
- Diagnostic collection is aware of Dynatrace official repositories
- Build workflow would not link to upload & activate commands
- Workflow for creating an extension overview dashboard (landing page)
- Build workflow can now build Python extension too (needs
dt-sdkavailable globally) - Code Actions for inserting filtering blocks and filters within entity lists
- Code Actions for inserting actions within screens
- Selector code lenses are much faster
- Suggestions related to entity attributes are correctly de-duplicated
- Selector code lenses would sometimes make the extension unresponsive
- Fast Development Mode availabe (read the docs what it is and how to enable)
- Code Lenses for Prometheus extensions allowing to scrape and endpoint
- Auto-completaions for metric and dimension values from prometheus scraped data as well as descriptions (in metadata)
- Code Actions for inserting metric, dimension, and metadata definitions from prometheus scraped data
- Code Actions for inserting entire entity screens
- First diagnostic items raised around extension name
- Build process uses diagnostics collection to decide if extension is ready to build
- Extension version is auto-incremented if version already exists in tenant
- Generated entity lists include a filter by entity name
- Actions and completions should trigger more often as extension parsing can handle incomplete/incorrect data better
- Selector statuses are now cached. They will only reset when they change. Known statuses won't require re-validation.
- Build & validation issues are communicated more clearly via JSON output
- Adding a new workspace would not trigger initialization correctly
- YAML re-writing does not fold lines
- Build process following the refactoring
- Code Lens for entity selectors similar to metric ones
- Settings to enable/disable code lenses for both metric and entity selectors
- Auto-completions for card keys in screen layouts and card lists
- Build command includes extension schema validation
- Errors from validating extension are shown in JSON in output panel
- Auto-completion suggestions are more readable
- Improved error communication to user via output panel
- Better status messging (loading indicators) in longer running commands
- Extension .zip archive is no longer produced for invalid extensions
- Settings have been refactored. See README.md to get new values.