@dx-do/cli 5.2.38 → 5.2.43

package/README.md

@@ -16,12 +16,8 @@ npx @dx-do/cli@<version> <--config=<config-file>> command-group command <paramet
 #### Output
 
 ```
-ℹ  info      dx-do v5.2.38 on node v24.14.1 on linux-x64 via node (ssl: 3.5.5)
-ℹ  info      Loading configuration from env DXDO_CONFIGURATION (base64)
-✔  success   Command line configuration complete
-ℹ  info      Allow Insecure HTTPS: false
-ℹ  info      DXSaasService instantiated.
-ℹ  info      Successfully configured.
+ℹ  info      dx-do v5.2.42 on node v22.21.0 on darwin-arm64 via node (ssl: 3.5.4)
+⚠  warning   Not loading configuration
 ✖  error     Usage: dx-do --option[=value]... <command-group> <command> <command-param>=<value>...
 ℹ  info      Available command-groups: agent, vertex, auth, dashboard, jsextension, axa, config, channel, alert, nass, alarm, apm-universe, o2-universe, trace, topographer, service, help, graph, metric, metrex, tas, experience, situation, sql, acc, o2-metricgrouping, o2-managementmodule, o2-alert, managementmodule, log, blob, perspective, metricgrouping, asm, inventory, event, attribute
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dx-do/cli",
-  "version": "5.2.38",
+  "version": "5.2.43",
   "description": "CLI execution of DX Operational Observability operations and triage",
   "author": "Ki Alam",
   "logo": {

package/dist-node/browseragent-snippet.template-9megjp8a.html

@@ -1,12 +0,0 @@
-<script
-        type="text/javascript"
-        id="ca_eum_ba"
-        src="${app.collectorURL}/api/1/urn:ca:tenantId:${app.tenantId}/urn:ca:appId:${app.appId}/bajs?agent=browser"
-        data-profileUrl="${app.collectorURL}/api/1/urn:ca:tenantId:${app.tenantId}/urn:ca:appId:${app.appId}/profile?agent=browser"
-        data-tenantID="${app.tenantId}"
-        data-appID="${app.appId}"
-        data-appVersion="1.0"
-        data-use-axa-appname="true"
-        data-appKey="${app.appKey}"
-        async
-></script>

package/dist-node/bulkvertexpatch-1a4qy5vb.md

@@ -1,78 +0,0 @@
-# dx-do bulk-vertex-patch
-
-The bulk vertex patch command ('vertex bulk-patch') is intended to ingest large
-amounts of attribute data from a json file, which will usually be generated by another script.
-
-The format of the json file is described in a json schema that is accessible with the bulk-patch-schema command (vertex bulk-patch-schema). 
-
-The top level of a bulk vertex patch is an object with three properties
-
-* **patchFilter**: a dictionary of attributeNames -> attributeValues.  Only objects that match this filter may be patched, regardless of the specific patch matching filters. 
-* **hostnameConfiguration**: default domain names for the source and vertex, to allow matching when the source or the vertex has a FQDN
-* **patches**: a list of patches, which are defined by attribute matching rules, new attributes to apply to matching vertices, and whether to overwrite existing attribute values.
-
-Here is a boilerplate bulk-patch file that defines a single patch.
-```json
-{
-   "patchFilter": {
-      "<attributeName1>": "<attributeValue>",
-      "<attributeName2>": "<attributeValue>"
-   },
-   "hostnameConfiguration": {
-      "patchHostDefaultDomain": "<.domain.name.com>",
-      "vertexHostDefaultDomain": "<.domain.name.com>"
-   },
-   "patches": [
-      {
-         "matches": [
-            {
-               "matchType": "DEFAULT_DOMAIN_MAPPING_HOST",
-               "attributeName": "hostname",
-               "matchValue": "lvnkprod010365"
-            }
-         ],
-         "newAttributeValues": {
-            "cmdb.ci.app": "2124451"
-         },
-         "overwrite": false
-      }
-   ]
-}
-
-```
-
-###
-
-| MatchType | Description                              |
-| --- |------------------------------------------|
-| DEFAULT_DOMAIN_MAPPING_HOST | see below                                |
-| ATTRIBUTE_EXACT | matches the exact value of the attribute |
-|ATTRIBUTE_PREFIX | matches the matchValue.*                 |
-
-
-### hostname configuration
-
-> Note the DEFAULT_DOMAIN_MAPPING_HOST strategy can be used on any attribute that has hostname-like values.
-
-If the patchHostDefaultDomain and the vertexHostDefaultDomain (both "domain.name.com") are the same, you will get the following match result:
-
-| patch source          | vertex attr value     | match |
-|-----------------------|-----------------------| --- |
-| host1                 | host1                 | true |
-| host1.domain.name.com | host1                 | true |
-| host1                 | host1.domain.name.com | true |
-| host1.another.domain  | host1 | false |
-| host1 | host1.another.domain | false |
-
-If the patchHostDefaultDomain and the vertexHostDefaultDomain are different ("d1.com" vs "d2.com"), you will get the following match result:
-
-
-
-| patch source (d1.com) | vertex attr value (d2.com) | match |
-|-----------------------|----------------------------|-------|
-| host1                 | host1                      | false |
-| host1.d1.com          | host1                      | false |
-| host1                 | host1.d1.com               | true  |
-| host1.d2.com          | host1                      | true  |
-
-

package/dist-node/bundle.pbd-38r15kyd.template

@@ -1,13 +0,0 @@
-SetFlag: ${flagName}
-
-#IdentifyClassAs: <class> ${flagName}
-#IdentifyInheritedAs: <class> ${flagName}
-#IdentifyAnnotatedClassAs: <class> ${flagName}
-#IdentifyDeepInheritedAs: <class> ${flagName}
-#IdentifyClassAs: <class> ${flagName}
-
-#TraceAnnotatedMethodsWithParametersIfFlagged: ${flagName} <AnnotationClass> BlamePointTracer "${metricRoot}|SubCategory"
-#TraceComplexMethodsIfFlagged: ${flagName} BlamePointTracer "${metricRoot}|SubCategory"
-#TraceComplexMethodsWithParametersIfFlagged: ${flagName} BlamePointTracer "${metricRoot}|SubCategory"
-#TraceOneMethodIfFlagged: ${flagName} <method> BlamePointTracer "${metricRoot}|SubCategory"
-#TraceOneMethodWithParametersIfFlagged: ${flagName} <method> BlamePointTracer "${metricRoot}|SubCategory"

package/dist-node/bundle.profile-1wpzpt3d.template

@@ -1,2 +0,0 @@
-${bundlePropertyRoot}.myProperty=false
-

package/dist-node/configuration-8c1w9b90.md

@@ -1,104 +0,0 @@
-
-## Environment Variables
-
-#### Basic Environment Vars
-
-* **DXDO_CONFIGURATION** : String containing entire JSON configuration
-* **DXDO_LOG_LEVEL** : "debug" or "info"
-* **DXDO_NO_COLOR** : disable colors in output
-* **FORCE_COLOR** : if 0 disable colors in logging
-* **DXDO_DEBUG_ARGS** : shows provided args as understood by the parser
-* **ALLOW_INSECURE_HTTPS** : allows connections to on-premise DX with self-signed certs.
-
-#### Request Logging Environment Vars
-
-* **DXDO_LOG_REQUESTS** : any value, true if exists.
-* **DXDO_REQUEST_LOG_FILE** : location to log requests
-* **DXDO_POSTMAN_EXPORT** : if set, along with DXDO_LOG_REQUESTS, will export a complete postman export of all network transactions.
-* **DXDO_POSTMAN_DIR** : set to the location for postman exports of runs
-
-## Configuration
-* dx-do loads its default configuration from ~/.dxdo/default.dxo2.config.json
-* If that doesn't exist, the first time you run dx-do, it will prompt you for values and write the configuration file.
-* You can have multiple config files for different tenants, and pass them using the '--config=<config file>' argument.
-* If your configuration file is in ~/.dxdo directory, you do not have to specify the directory' argument.
-* Also, dx-do assumes that the extension is .json and will add it if the file doesn't exist as specified.
-
-* ```'npx dx-do --config=my-config'``` will find a config in ```~/.dxdo/my-config.dxo2.config.json```
-
-## Proxy Configuration
-
-* dx-do relies on system proxy by default.
-* if a system proxy is enabled but not working, you can try setting
-  * `export GLOBAL_AGENT_HTTP_PROXY=true`
-* user can also provide a proxy configuration file on the command line
-  * 'npx dx-do --config=my-config --proxyConfig=my-proxy.json'
-
-###  Proxy configuration file format
-```text
-{
-    host: <proxy hostname>
-    port:  <proxy port>
-    auth: {
-       username: <username>
-       password: <password> 
-    }
-    protocol: <proxy http mode = "https" | "http">
-}
-
-```
-## Generating keys
-
-* [userToken]  Launchpad -> Settings -> + New Token -> User Token ...
-
-## optional configuration
-
-* userToken is now required, tenant token is not necessary.
-
-## current version 4 configuration file format
-
-```
-{
-  "configurationVersion": "3"
-  "cohortId": "<cohortUD from Settings -> Connector Parameters>",
-  "userToken": <DX User Token from Settings -> Manage Tokens -> New Token -> User>,
-  "dxGatewayHost": "https://apmgw.dxi-na1.saas.broadcom.com/",
-}
-```
-
-
-## now disabled version 3 configuration file format, please use "config upgrade" command.
-
-```
-{
-  "tenantCN": "<>",
-  "tenantId": "<>",
-  "tenantToken": <DX Tenant Token>,
-  "userToken": <DX User Token>,
-  "hostUrl": "https://apmgw.dxi-na1.saas.broadcom.com/",
-  "axaHostUrl": "https://axa.dxi-na1.saas.broadcom.com/",
-  "oiHostUrl": "https://oi.dxi-na1.saas.broadcom.com/",
-  "axaSessionHostUrl": "https://axaservices-es-exporter.dxi-na1.saas.broadcom.com/",
-  "dashboardHostUrl": "https://dxi-dashboard.dxi-na1.saas.broadcom.com/",
-  "configurationVersion": "3"
-}
-```
-
-## disabled old configuration file format
-
-```
-{
-  "tenantToken": <DX Tenant Token> 
-  "hostUrl": <DX APM Host>,
-  "axaHostUrl"?: <DX AXA Host>,
-  "oiHostUrl"?: <DX OI Host>,
-  "tenantId": <DX Tenant Number>,
-  "tenantCN": <DX Tenant Name>>,
-  "dashboardHostUrl"?: <DX Dashboard Host>,
-  "dashboardApiKey"?: <Deprecated: DX Dashboard Key -- see 'npx dx-do dashboard create-dashboard-api-key'>,
-  "oiUserKey"?: <DX User API Key: Deprecated>
-  "apiKey": <DX User Key -- Not used since 2.9>,
-}
-```
-
-

package/dist-node/dashboards-x0xddksy.md

@@ -1,17 +0,0 @@
-# dx-do dashboard quirks
-
-### Configuration
-
-dx-do dashboard commands require an API key that is not able to be generated from the UI. 
-
-In order to generate a dashboard api key, follow these steps:
-
-1. Open a modern browser as a DX admin
-2. Open browser developer tools and find any XHR request ("search").
-3. In the request headers, ensure that it has keys starting with CA_ and SPP_
-4. Copy the entire cookie value.
-5. From the terminal, run
-   * ```npx dx-do dashboard create-dashboard-api-key liveBrowserSessionCookie="<paste cookie header>"```
-6. Add a key "dashboardApiKey" to your tenant's config.json with the value generated by the previous command.
-
-

package/dist-node/default-licensing-config-0p879qpb.template

@@ -1,122 +0,0 @@
-{
-  "licenseGroups": [
-    {
-      "name": "Kubernetes",
-      "isPrimary": true,
-      "devicesPerHost": 4,
-      "membershipRules": [
-        {
-          "agentNameRegex": "Kubernetes Agent.*"
-        }
-      ]
-    },{
-      "name": "Java",
-      "isPrimary": true,
-      "devicesPerAgent": 4,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(tomcat|weblogic|websphere|undertow|liberty).*"
-        }
-      ]
-    },
-    {
-      "name": ".NET",
-      "isPrimary": true,
-      "devicesPerAgent": 4,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(\\.NET).*",
-          "excludeAgentNameRegex": "PerfMonCollector.*"
-        }
-      ]
-    },
-    {
-      "name": "NodeJS",
-      "isPrimary": true,
-      "devicesPerAgent": 0.4,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(nodejs-).*"
-        }
-      ]
-    },
-    {
-      "name": "Go",
-      "isPrimary": true,
-      "devicesPerAgent": 0.4,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(go-).*"
-        }
-      ]
-    },
-    {
-      "name": "Python",
-      "isPrimary": true,
-      "devicesPerHost": 4,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(python-).*"
-        }
-      ]
-    },{
-      "name": "PHP",
-      "isPrimary": true,
-      "devicesPerAgent": 4,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(php-).*"
-        }
-      ]
-    },
-    {
-      "name": "NetOps",
-      "isPrimary": true,
-      "devicesPerAgent": 0,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(NFA|NetOps|Spectrum|VNA).*"
-        }
-      ]
-    },
-    {
-      "name": "Infrastructure",
-      "isPrimary": false,
-      "devicesPerAgent": 1,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(Infrastructure).*"
-        },
-        {
-          "agentProcessRegex": "Cluster.*"
-        },
-        {
-          "agentNameRegex": "Infrastructure.*"
-        },
-        {
-          "agentNameRegex": "Prometheus.*"
-        }
-      ]
-    },
-    {
-      "name": "PerfMon",
-      "isPrimary": false,
-      "devicesPerAgent": 1,
-      "membershipRules": [
-        {
-          "agentProcessRegex": "(PerfMonCollector).*"
-        }
-      ]
-    },
-    {
-      "name": "Built-In",
-      "isPrimary": false,
-      "devicesPerGroupMember": 0,
-      "membershipRules": [
-        {
-          "agentHostRegex": "(Custom Metric Host|Experience Collector Host)"
-        }
-      ]
-    }
-  ]
-}

package/dist-node/description.md-qwc2bj9r.template

@@ -1,30 +0,0 @@
-# ${bundleName} (${bundleVersion})
-
-## Description
-
-${bundleDisplayName}
-
-## APM version
-${agentMinimumVersion}
-
-## Supported third party versions
-
-## Limitations
-
-## License
-https://communities.ca.com/docs/DOC-231150910#license on the CA APM Developer Community.
-
-## Support
-This document and associated tools are made available from CA Technologies as examples and provided at no charge as a courtesy to the CA APM Community at large. This resource may require modification for use in your environment. However, please note that this resource is not supported by CA Technologies, and inclusion in this site should not be construed to be an endorsement or recommendation by CA Technologies. These utilities are not covered by the CA Technologies software license agreement and there is no explicit or implied warranty from CA Technologies. They can be used and distributed freely amongst the CA APM Community, but not sold. As such, they are unsupported software, provided as is without warranty of any kind, express or implied, including but not limited to warranties of merchantability and fitness for a particular purpose. CA Technologies does not warrant that this resource will meet your requirements or that the operation of the resource will be uninterrupted or error free or that any defects will be corrected. The use of this resource implies that you understand and agree to the terms listed herein.
-
-Although these utilities are unsupported, please let us know if you have any problems or questions by adding a comment to the CA APM Community Site area where the resource is located, so that the Author(s) may attempt to address the issue or question.
-
-Unless explicitly stated otherwise this field pack is only supported on the same platforms as the APM core agent. See [APM Compatibility Guide](http://www.ca.com/us/support/ca-support-online/product-content/status/compatibility-matrix/application-performance-management-compatibility-guide.aspx).
-
-
-# Change log
-Changes for each version of the field pack.
-
-Version | Author | Comment
-|--------|--------|--------|
-|${bundleVersion}| ${bundleAuthor} | First version of the field pack.|

package/dist-node/installInstructions.md-k9ghf3dr.template

@@ -1,21 +0,0 @@
-# ${bundleName} (${bundleVersion})
-
-## Description
-
-${bundleDisplayName}
-
-# Installation Instructions
-
-deploy to extensions/deploy in the agent directory or add to a package via ACC.
-
-## Prerequisites
-
-## Dependencies
-${bundleDependencies}
-
-## Configuration
-
-# Usage Instructions
-
-## Debugging and Troubleshooting
-