### Pass configuration parameters during installation Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/oneagent-configuration-via-command-line-interface Examples of passing configuration parameters during the initial installation of OneAgent. ```bash /bin/sh Dynatrace-OneAgent-Linux.sh –-set-host-group=test_group ``` ```bash Dynatrace-OneAgent-Windows.exe --set-host-group=test_group ``` ```bash Dynatrace-OneAgent-Windows.msi ADDITIONAL_CONFIGURATION="--set-host-group=test_group" ``` -------------------------------- ### SSM Distributor Configuration Example Source: https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-into-aws/aws-ec2/deploy-oneagent-using-aws-systems-manager-distributor Example of additional arguments for the Systems Manager Run Command during package installation. ```json { "SSM_DYNATRACE_URL" : "https://your-tenant.live.dynatrace.com/", "SSM_DYNATRACE_HOST_GROUP" : "MY-HOST-GROUP", "SSM_DYNATRACE_MONITORING_MODE" : "infra-only", "SSM_DYNATRACE_APP_LOG_CONTENT_ACCESS" : "true", "SSM_DYNATRACE_TOKEN_SECRET_ID" : "dynatrace-paas-token" } ``` -------------------------------- ### Pass installation parameters for EXE installer Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/installation-and-operation/windows/installation/customize-oneagent-installation-on-windows Example of appending configuration parameters to the OneAgent EXE installer command. ```powershell .\Dynatrace-OneAgent-Windows.exe --set-host-group=my_host_group --set-monitoring-mode=infra-only INSTALL_PATH="C:\installdir" ``` -------------------------------- ### Installation Output Log Source: https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-into-aws/aws-ec2/deploy-oneagent-using-aws-systems-manager-distributor Example output showing a successful installation of the Dynatrace OneAgent on Windows. ```text Initiating DynatraceOneAgent_ 1.0.51 install Plugin aws:runPowerShellScript ResultStatus Success install output: Running install.ps1 Installing Dynatrace OneAgent on Windows... script version: 1.0.51 Configuration parameters: - Dynatrace URL: https://environment.live.dynatrace.com/ --quiet Installing Dynatrace Package on Windows... - downloading agent from: https://environment.live.dynatrace.com/ to: %PROGRAMDATA%\Amazon\SSM\Packages\DynatraceOneAgent_\1.0.51\Dynatrace-OneAgent-Windows.exe - running installation - cleaning up Done Successfully installed DynatraceOneAgent_ 1.0.51 ``` -------------------------------- ### Troubleshoot command output example Source: https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/troubleshooting Example output showing a successful validation of the Dynatrace Operator setup. ```text {"level":"info","ts":"2022-09-12T08:45:21.437Z","logger":"dynatrace-operator-version","msg":"dynatrace-operator","version":"","gitCommit":"","buildDate":"","goVersion":"","platform":""} [namespace ] --- checking if namespace 'dynatrace' exists ... [namespace ] √ using namespace 'dynatrace' [dynakube ] --- checking if 'dynatrace:dynakube' Dynakube is configured correctly [dynakube ] CRD for Dynakube exists [dynakube ] using 'dynatrace:dynakube' Dynakube [dynakube ] checking if api url is valid [dynakube ] api url is valid [dynakube ] checking if secret is valid [dynakube ] 'dynatrace:dynakube' secret exists [dynakube ] secret token 'apiToken' exists [dynakube ] customPullSecret not used [dynakube ] pull secret 'dynatrace:dynakube-pull-secret' exists [dynakube ] secret token '.dockerconfigjson' exists [dynakube ] proxy secret not used [dynakube ] √ 'dynatrace:dynakube' Dynakube is valid [dtcluster ] --- checking if tenant is accessible ... [dtcluster ] √ tenant is accessible ``` -------------------------------- ### Configure direct download variables Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/deployment-orchestration/ansible Example variables for authenticating with the Dynatrace environment to download installers directly. ```yaml # Set environment variables oneagent_environment_url: 'https://your-environment.live.dynatrace.com' oneagent_paas_token: 'abcdefjhij1234567890' ``` -------------------------------- ### Example: Install ActiveGate with Custom CA Certificate Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/installation/windows/windows-customize-installation-for-activegate An example command demonstrating how to install ActiveGate on Windows while specifying both the custom CA certificate file and its password file. ```bash C:\Dynatrace-ActiveGate-Windows-x86-.exe CA_CERTIFICATE_FILE=D:\Users\Fred\myCert.jks CA_CERTIFICATE_PASSWORD_FILE=D:\Users\Fred\myPwd.txt ``` -------------------------------- ### Start the Sample Application Source: https://docs.dynatrace.com/docs/observe/dynatrace-for-ai-observability/sample-use-cases/openai-observability Run the command to start both the frontend and backend of the sample application. The frontend will be accessible at http://localhost:3000. ```bash npm run dev ``` -------------------------------- ### POST /virtual-machines/start Source: https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/azure/azure-workflows-actions-compute Starts a virtual machine. ```APIDOC ## POST /virtual-machines/start ### Description The operation to start a virtual machine. ### Parameters #### Path Parameters - **subscriptionId** (string) - Required - The ID of the target subscription. - **resourceGroupName** (string) - Required - The name of the resource group. - **vmName** (string) - Required - The name of the virtual machine. ``` -------------------------------- ### Manual Pub/Sub instrumentation setup Source: https://docs.dynatrace.com/docs/ingest-from/google-cloud-platform/gcp-integrations/gcp-functions/opentelemetry-on-gcf-go Initial imports and constants for manual Pub/Sub instrumentation. ```go package instrumentation import ( "context" "fmt" "go.opentelemetry.io/otel" "go.opentelemetry.io/otel/codes" "go.opentelemetry.io/otel/propagation" semconv "go.opentelemetry.io/otel/semconv/v1.10.0" "go.opentelemetry.io/otel/trace" cloudevents "github.com/cloudevents/sdk-go/v2/event" ) const ( ``` -------------------------------- ### Application Start Query Source: https://docs.dynatrace.com/docs/semantic-dictionary/versions/id-1-317/model/user-events Example query to search for all application starts using Dynatrace RUM. ```APIDOC ## Application Start Query ### Description This query searches for all application starts. ### Query ``` fetch user.events | filter characteristics.has_app_start == true ``` ``` -------------------------------- ### Application Setup and Run Source: https://docs.dynatrace.com/docs/observe/dynatrace-for-ai-observability/sample-use-cases/self-service-ai-observability-tutorial Initializes the retrieval chain, mounts static files, and runs the FastAPI application using uvicorn. Ensure the './public' directory exists for static files. ```python if __name__ == "__main__": retrieval_chain = prep_system() # Mount static files at the root app.mount("/", StaticFiles(directory="./public", html=True), name="public") #app.mount("/destinations", StaticFiles(directory="destinations", html = True), name="destinations") # Run the app using uvicorn uvicorn.run(app, host="0.0.0.0", port=8080) ``` -------------------------------- ### OS Version Examples Source: https://docs.dynatrace.com/docs/semantic-dictionary/versions/id-1-320/model/security-events Examples of complete OS versions, including patch, build, and other information. ```text 15.3.1 ``` ```text Ubuntu 16.04.7 LTS (Xenial Xerus) (kernel 4.15.0-206-generic) ``` ```text Windows Server 2022 Datacenter 21H2 2009, ver. 10.0.20348 ``` -------------------------------- ### Show General Help (Example) Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/agctl-command-line-interface Example of how to display general help for agctl. ```bash # Show general help agctl help ``` -------------------------------- ### GET /user.events (Application Start) Source: https://docs.dynatrace.com/docs/semantic-dictionary/model/rum/user-events/navigation-related Retrieves application start events using the Dynatrace query language. ```APIDOC ## GET /user.events ### Description Retrieves all application start events from the RUM data store. ### Method GET ### Endpoint /user.events ### Query Parameters - **filter** (string) - Required - The filter expression: `characteristics.has_app_start == true` ### Request Example fetch user.events | filter characteristics.has_app_start == true ### Response #### Success Response (200) - **characteristics.classifier** (string) - Fixed value 'app_start' - **characteristics.has_app_start** (boolean) - Fixed value 'true' - **characteristics.has_navigation** (boolean) - Fixed value 'true' - **app_start.type** (string) - The type of app start ('cold', 'warm', 'hot') - **app_start.start_time** (duration) - Start time relative to event start_time - **app_start.end_time** (duration) - End time relative to event start_time ``` -------------------------------- ### Example Deployment Output Source: https://docs.dynatrace.com/docs/deliver/configuration-as-code/monaco/monaco-getting-started Sample log output indicating a successful deployment. ```text time=2025-09-01T09:08:23.506+02:00 level=INFO msg="Monaco version 2.24.0" time=2025-09-01T09:08:23.507+02:00 level=INFO msg="Loading manifest \"{your full path to the file}\manifest.yaml\". Restrictions: groups=[], environments=[]" manifestPath="{your full path to the file}\manifest.yaml" time=2025-09-01T09:08:23.535+02:00 level=INFO msg="Projects to be deployed (1):" time=2025-09-01T09:08:23.536+02:00 level=INFO msg=" - my-slo-project" time=2025-09-01T09:08:23.536+02:00 level=INFO msg="Environments to deploy to (1):" time=2025-09-01T09:08:23.537+02:00 level=INFO msg=" - development-environment" time=2025-09-01T09:08:23.537+02:00 level=INFO msg="Deploying configurations to environment \"development-environment\"..." environment.name=default environment.group=group time=2025-09-01T09:08:23.556+02:00 level=INFO msg="Deploying config" deploymentStatus=deploying environment.name=development-environment environment.group=group coordinate.reference=my-slo-project:slo-v2:my-sample-slo coordinate.project=my-slo-project coordinate.type=slo-v2 coordinate.configId=my-sample-slo gid=0 time=2025-09-01T09:08:23.557+02:00 level=INFO msg="Deployment successful" deploymentStatus=deployed environment.name=development-environment environment.group=group coordinate.reference=my-slo-project:slo:my-sample-slo coordinate.project=my-slo-project coordinate.type=slo-v2 coordinate.configId=my-sample-slo gid=0 time=2025-09-01T09:08:23.557+02:00 level=INFO msg="Deployment successful for environment 'development-environment'" environment.group=group environment.name=development-environment environment.name=development-environment environment.group=group time=2025-09-01T09:08:23.557+02:00 level=INFO msg="Deployment finished without errors" ``` -------------------------------- ### Example - GET /api/v2/synthetic/locations/{syntheticLocationId} (Private Location) Source: https://docs.dynatrace.com/docs/dynatrace-api/environment-api/synthetic-v2/synthetic-locations-v2/get-a-location Example of retrieving details for a private synthetic location. ```APIDOC ## Example - private location ### Method GET ### Endpoint /api/v2/synthetic/locations/SYNTHETIC_LOCATION-BB5EE23C1D48AFF5 ### Request Example ```bash curl -X GET \ https://mySampleEnv.live.dynatrace.com/api/v2/synthetic/locations/SYNTHETIC_LOCATION-BB5EE23C1D48AFF5 \ -H 'Authorization: Api-Token dt0c01.abc123.abcdefjhij1234567890' ``` ### Response Example ```json { "entityId": "SYNTHETIC_LOCATION-BB5EE23C1D48AFF5", "type": "PRIVATE", "name": "Linz HTTP", "countryCode": "AT", "regionCode": "04", "city": "Linz", "latitude": 48.306351, "longitude": 14.287399, "status": "ENABLED", "nodes": [ "137829320" ], "availabilityLocationOutage": false, "availabilityNodeOutage": false, "locationNodeOutageDelayInMillis": 3000, "geoLocationId": "GEOLOCATION-427705B3488A4C45" } ``` ``` -------------------------------- ### Define configuration order using dependencies Source: https://docs.dynatrace.com/docs/deliver/configuration-as-code/monaco/guides/order-of-configurations This example demonstrates a standard config.yaml setup for two app detection rules without explicit ordering. ```yaml configs: - id: rule2 config: name: rule2 template: rule2.json skip: false type: settings: schema: builtin:rum.web.app-detection schemaVersion: 2.0.1 scope: environment - id: rule1 config: name: rule1 template: rule1.json skip: false type: settings: schema: builtin:rum.web.app-detection schemaVersion: 2.0.1 scope: environment ``` ```yaml configs: - id: rule2 config: name: rule2 template: rule2.json skip: false parameters: order: configId: rule1 property: id type: reference type: settings: schema: builtin:rum.web.app-detection schemaVersion: 2.0.1 scope: environment - id: rule1 config: name: rule1 template: rule1.json skip: false type: settings: schema: builtin:rum.web.app-detection schemaVersion: 2.0.1 scope: environment ``` -------------------------------- ### Instrumenting Applications with OpenKit Source: https://docs.dynatrace.com/docs/ingest-from/extend-dynatrace/openkit/instrument-your-application-using-dynatrace-openkit Examples demonstrating how to initialize the OpenKit builder, manage sessions, identify users, and track actions. Ensure you use the specific Beacon URL and Application ID provided in the Dynatrace instrumentation wizard. ```Java // Obtain an OpenKit instance String applicationID = "application-id"; // Your application's ID long deviceID = 42; // Replace with a unique value per device/installation String endpointURL = "https://tenantid.beaconurl.com/mbeacon"; // Dynatrace endpoint URL OpenKit openKit = new DynatraceOpenKitBuilder(endpointURL, applicationID, deviceID) .withApplicationVersion("1.0.0.0") .withOperatingSystem("Windows 10") .withManufacturer("MyCompany") .withModelID("MyModelID") .build(); // Wait up to 10 seconds for OpenKit to complete initialization long timeoutInMilliseconds = 10 * 1000; boolean success = openKit.waitForInitCompletion(timeoutInMilliseconds); // Create session String clientIP = "8.8.8.8"; Session session = openKit.createSession(clientIP); // Identify user session.identifyUser("jane.doe@example.com"); // Create root and child actions String rootActionName = "rootActionName"; RootAction rootAction = session.enterAction(rootActionName); String childActionName = "childAction"; Action childAction = rootAction.enterAction(childActionName); // Leave action childAction.leaveAction(); rootAction.leaveAction(); // Finish session session.end(); // Terminate OpenKit instance openKit.shutdown(); ``` ```.NET // Obtain an OpenKit instance string applicationID = "application-id"; // Your application's ID long deviceID = 42L; // Replace with a unique value per device/installation string endpointURL = "https://tenantid.beaconurl.com/mbeacon"; // Dynatrace endpoint URL IOpenKit openKit = new DynatraceOpenKitBuilder(endpointURL, applicationID, deviceID) .WithApplicationVersion("1.0.0.0") .WithOperatingSystem("Windows 10") .WithManufacturer("MyCompany") .WithModelID("MyModelID") .Build(); // Wait up to 10 seconds for OpenKit to complete initialization int timeoutInMilliseconds = 10 * 1000; bool success = openKit.WaitForInitCompletion(timeoutInMilliseconds); // Create session string clientIP = "8.8.8.8"; ISession session = openKit.CreateSession(clientIP); // Identify user session.IdentifyUser("jane.doe@example.com"); // Create root and child actions string rootActionName = "rootActionName"; IRootAction rootAction = session.EnterAction(rootActionName); string childActionName = "childAction"; IAction childAction = rootAction.EnterAction(childActionName); // Leave action childAction.LeaveAction(); rootAction.LeaveAction(); // Finish session session.End(); // Terminate OpenKit instance openKit.ShutDown(); ``` ```C++ // Obtain an OpenKit instance const char* applicationID = "application-id"; // Your application's ID int64_t deviceID = 42; // Replace with a unique value per device/installation const char* endpointURL = "https://tenantid.beaconurl.com/mbeacon"; // Dynatrace endpoint URL std::shared_pointer openKit = openkit::DynatraceOpenKitBuilder(endpointURL, applicationID, deviceID) .withApplicationVersion("1.0.0.0") .withOperatingSystem("Windows 10") .withManufacturer("MyCompany") .withModelID("MyModelID") .build(); // Wait up to 10 seconds for OpenKit to complete initialization int64_t timeoutInMilliseconds = 10 * 1000; bool success = openKit->waitForInitCompletion(timeoutInMilliseconds); // Create session const char* clientIP = "8.8.8.8"; std::shared_ptr session = openKit->createSession(clientIP); // Identify user session->identifyUser("jane.doe@example.com"); // Create root and child actions const char* rootActionName = "rootActionName"; std::shared_ptr rootAction = session->enterAction(rootActionName); const char* childActionName = "childAction"; ``` -------------------------------- ### GET /user.events (Application Start Query) Source: https://docs.dynatrace.com/docs/semantic-dictionary/versions/id-1-320/model/user-events Retrieves all application start events using the Dynatrace query language. ```APIDOC ## GET /user.events ### Description Searches for all application start events in the RUM data. ### Method GET ### Endpoint /user.events ### Request Example ``` fetch user.events | filter characteristics.has_app_start == true ``` ``` -------------------------------- ### Install OpenTelemetry PHP library Source: https://docs.dynatrace.com/docs/ingest-from/opentelemetry/walkthroughs/php/php-auto Use pickle to build and install the instrumentation library. ```bash php pickle.phar install opentelemetry ``` -------------------------------- ### Configure OneAgent Installation Source: https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-azure-app-service Starts the OneAgent installation or upgrade with the specified settings. Settings are stored only upon successful installation. Leave `apiUrl` empty for SaaS environments. ```json { "apiUrl": "", "apiToken": "", "environmentId": "", "sslMode": "AcceptAll" } ``` -------------------------------- ### Get OneAgent Installation Status Source: https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-azure-app-service Retrieves the current status of the OneAgent installation. Use the `isAgentInstalled` and `isUpgradeAvailable` fields for automation. ```json { "state": "Installed", "message": "OneAgent installed", "version": "1.157", "isAgentInstalled": true, "isUpgradeAvailable": false, "isFunction": false, "functionAppSettings": null } ``` -------------------------------- ### Start OneAgent with an Active Activity (Kotlin) Source: https://docs.dynatrace.com/docs/observe/digital-experience/mobile-applications/instrument-android-app/instrumentation-via-oneagent-sdk/oneagent-sdk-for-android This Kotlin example demonstrates starting OneAgent with an active Activity, allowing for immediate monitoring of that specific Activity. It's an alternative to starting in Application.onCreate. ```kotlin Dynatrace.startup(yourActiveActivity, DynatraceConfigurationBuilder("", "") ... // additional configuration .buildConfiguration()) ``` -------------------------------- ### Build and Instrument Project Source: https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/mobile-frontends/react-native/id-01-initial-setup Commands to prepare the project, instrument native files, and run the application. ```bash npx expo prebuild ``` ```bash npx instrumentDynatrace ``` ```bash react-native run-android # or react-native run-ios ``` -------------------------------- ### Install Python Backend Dependencies Source: https://docs.dynatrace.com/docs/observe/dynatrace-for-ai-observability/sample-use-cases/openai-observability Navigate to the python-backend directory, create a virtual environment, activate it, and install the required Python packages using pip. This prepares the backend for running the sample application. ```bash cd python-backend python3.12 -m venv .venv source .venv/bin/activate pip install -r requirements.txt ``` -------------------------------- ### SDLC Validation Events Query Examples Source: https://docs.dynatrace.com/docs/semantic-dictionary/versions/id-1-326/model/sdlc-events Examples for querying SDLC validation events, which are generated when a validation is started or finished in a CI/CD context. ```APIDOC ### Query all SDLC validation task events ``` fetch events | filter event.kind == "SDLC_EVENT" and event.category == "task" and event.type == "validation" ``` ### Query all SDLC validation started task events ``` fetch events | filter event.kind == "SDLC_EVENT" and event.category == "task" and event.type == "validation" and event.status == "started" ``` ### Query all SDLC validation finished task events ``` fetch events | filter event.kind == "SDLC_EVENT" and event.category == "task" and event.type == "validation" and event.status == "finished" ``` ``` -------------------------------- ### Example of a version 1.x project folder structure Source: https://docs.dynatrace.com/docs/deliver/configuration-as-code/monaco/guides/deprecated-migration Displays the standard directory layout for a version 1.x project. ```text workdir/ project/ app-detection-rule/ ... dashboard/ config.json config.yaml environment.yaml ``` -------------------------------- ### Start PurePath Distributed Trace (COBOL) Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/installation-and-operation/zos/operation/cics-ims-sdk COBOL examples for starting a new CICS or IMS distributed trace using the DTSP and DTSPTF calls. ```COBOL CALL "DTSP" RETURNING RC. CALL "DTSPTF" USING FIXED_LEN_STRING, LENGTH, CCSID RETURNING RC. ``` -------------------------------- ### Example of a project folder structure with version 2 migration Source: https://docs.dynatrace.com/docs/deliver/configuration-as-code/monaco/guides/deprecated-migration Shows the folder structure after adding version 2 configurations alongside legacy ones. ```text workdir/ project/ app-detection-rule-v2/ ... dashboard/ config.json config.yaml dashboard-v2/ config.json config.yaml environment.yaml ``` -------------------------------- ### Get all SDLC validation started task events Source: https://docs.dynatrace.com/docs/semantic-dictionary/model/sdlc-events This query filters for SDLC validation task events that have a status of 'started'. It requires `event.kind` to be `SDLC_EVENT`. ```dql fetch events | filter event.kind == "SDLC_EVENT" and event.category == "task" and event.type == "validation" and event.status == "started" ``` -------------------------------- ### PUT /api/settings Source: https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-azure-app-service Configures and starts the OneAgent installation using the provided settings. ```APIDOC ## PUT /api/settings ### Description Starts OneAgent installation with the given settings. These settings are stored only if the installation finishes successfully. This endpoint can also be used to trigger an upgrade. ### Method PUT ### Endpoint /dynatrace/api/settings ### Request Body - **environmentID** (string) - Required - The environment ID - **APIToken** (string) - Required - The PaaS token - **APIUrl** (string) - Optional - The server URL - **SSLMode** (string) - Optional - TLS certificate mode (Default or all) - **networkZone** (string) - Optional - Network zone - **monitoredCLR** (string) - Optional - CLR type (clr, coreclr, or both) ### Response #### Success Response (200) - Empty response ``` -------------------------------- ### Example of Setting a Node Label Source: https://docs.dynatrace.com/docs/observe/digital-experience/synthetic-monitoring/private-synthetic-locations/containerized-locations An example demonstrating how to label a node with a specific zone. ```bash kubectl label nodes ip-10-179-202-73.ec2.internal zone=us-east-1a ``` -------------------------------- ### Get ActiveGate Version Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-activegate/agctl-command-line-interface Retrieve the current version information for the ActiveGate installation. ```bash agctl version get ``` -------------------------------- ### Initialize project directory Source: https://docs.dynatrace.com/docs/deliver/configuration-as-code/monaco/monaco-getting-started Create the necessary directory structure for a new Monaco project. ```bash mkdir -p monaco-getting-started/project-example/slo cd monaco-getting-started/project-example/slo ``` -------------------------------- ### Startup with Additional Options in Swift Source: https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/mobile-frontends/ios/id-03-configuration Pass additional configuration options during manual startup using dictionary keys. Values passed here take precedence over Info.plist settings. ```swift Dynatrace.startupWithConfig([ kDTXApplicationID: "YOUR_APPLICATION_ID", kDTXBeaconURL: "https://your-environment.dynatrace.com/mbeacon", kDTXCrashReportingEnabled: true, kDTXLogLevel: "INFO", kDTXAllowAnyCert: false, kDTXUserOptIn: false ]) ``` -------------------------------- ### SDLC deployment started task event fields Source: https://docs.dynatrace.com/docs/semantic-dictionary/model/sdlc-events This section details the fields used for SDLC deployment started task events, including their types, descriptions, and examples. ```APIDOC ## SDLC deployment started task event fields ### Description Provides details about the fields for SDLC deployment started task events. ### Parameters #### Request Body - **cicd.deployment.id** (string) - experimental - The identifier of the deployment. - **cicd.deployment.name** (string) - experimental - The name of the deployment. - **cicd.deployment.namespace** (string) - experimental - The destination namespace where the deployment resource is created. - **cicd.deployment.release_stage** (string) - experimental - The name of the deployment environment, also known as deployment tier. - **cicd.deployment.server.url.full** (string) - experimental - The deployment server URL. - **cicd.deployment.service.id** (string) - experimental - The identifier of the service that is deployed. - **event.category** (string) - experimental - Describes the SDLC event's category, which must be set to `task` for SDLC task events. - **event.id** (string) - experimental - Unique identifier string of an event; is stable across multiple refreshes and updates. - **event.kind** (string) - experimental - Gives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event. - **event.provider** (string) - experimental - Source of the event, for example, the name of the component or system that generated the event. - **event.status** (string) - experimental - The value must be set to `started` for SDLC deployment started task events. - **event.type** (string) - experimental - The value must be set to `deployment` for any task event describing a deployment in the software development lifecycle. - **event.version** (string) - experimental - The version of the SDLC deployment started task event. - **start_time** (timestamp) - experimental - The time (UNIX Epoch time in nanoseconds) when the deployment task was started. - **task.id** (string) - experimental - The unique task identifier. - **task.name** (string) - experimental - A human-readable name for a task. - **timestamp** (timestamp) - experimental - The time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created. - **vcs.ref.base.name** (string) - experimental - The name of the reference in the repository. This can be a branch name or a tag name. - **vcs.ref.base.revision** (string) - experimental - The revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. - **vcs.repository.url.full** (string) - experimental - The repository's full URL. ### Request Example ```json { "cicd.deployment.id": "1337", "cicd.deployment.name": "deploy frontend app", "cicd.deployment.namespace": "default", "cicd.deployment.release_stage": "development", "cicd.deployment.server.url.full": "https://kubernetes.default.svc", "cicd.deployment.service.id": "92ba59d6-379e-4ffd-a67e-d544a9c24dea", "event.category": "task", "event.id": "5547782627070661074_1647601320000", "event.kind": "SDLC_EVENT", "event.provider": "argocd", "event.status": "started", "event.type": "deployment", "event.version": "0.1.0", "start_time": 1649822520123123123, "task.id": "123", "task.name": "CI build my-service", "timestamp": 1649822520123123123, "vcs.ref.base.name": "my-branch-name", "vcs.ref.base.revision": "d4322ab6cba38d21ad83c9de304a6a214ecf2cdc", "vcs.repository.url.full": "https://github.com/dynatrace-oss/terraform-provider-dynatrace" } ``` ``` -------------------------------- ### Example Log with Single Application Format Source: https://docs.dynatrace.com/docs/analyze-explore-automate/logs/lma-log-ingestion/lma-log-ingestion-via-oa/lma-log-entry-boundary This example shows a log created by a single application, demonstrating the expected format before applying entry boundary rules. ```text Timestamp - 2024.10.01 9:30:00 Third line First line Timestamp - 2024.10.01 9:31:00 Third line First line Timestamp - 2024.10.01 9:32:00 Third line First line Timestamp - 2024.10.01 9:33:00 Third line ``` -------------------------------- ### Start PurePath Distributed Trace (C) Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/installation-and-operation/zos/operation/cics-ims-sdk C examples for starting a new CICS or IMS distributed trace using DTSP, DTSPTN, DTSPTP, and DTSPTF functions. ```C int DTSP (void); int DTSPTN (const char* c_string, const int* ccsid); int DTSPTP (const void* pli_string, const int* ccsid); int DTSPTF (const char* fixed_len_string, const int* length, const int* ccsid); ``` -------------------------------- ### Start PurePath Distributed Trace (PL/I) Source: https://docs.dynatrace.com/docs/ingest-from/dynatrace-oneagent/installation-and-operation/zos/operation/cics-ims-sdk PL/I examples for starting a new CICS or IMS distributed trace using DTSP, DTSPTN, DTSPTP, and DTSPTF calls. ```PL/I rc = DTSP(); rc = DTSPTN(c_string, ccsid); rc = DTSPTP(pli_string, ccsid); rc = DTSPTF(fixed_len_string, length, ccsid); ``` -------------------------------- ### Implement React Navigation structure Source: https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/mobile-frontends/react-native/id-05-app-performance Example setup using @react-navigation/drawer and @react-navigation/stack to demonstrate how view contexts are generated based on navigation routes. ```javascript import { NavigationContainer } from '@react-navigation/native'; import { createDrawerNavigator } from '@react-navigation/drawer'; import { createStackNavigator } from '@react-navigation/stack'; const Drawer = createDrawerNavigator(); function App() { return ( ); } const Stack = createStackNavigator(); function FeatureScreen() { return ( ); } ``` -------------------------------- ### Get Current Time Source: https://docs.dynatrace.com/docs/platform/grail/dynatrace-query-language/functions/time-functions Returns the current time as a fixed timestamp at the start of the query. ```DQL data record() | fieldsAdd now() ``` -------------------------------- ### Startup with Additional Options in Objective-C Source: https://docs.dynatrace.com/docs/observe/digital-experience/new-rum-experience/mobile-frontends/ios/id-03-configuration Pass additional configuration options during manual startup using dictionary keys. Values passed here take precedence over Info.plist settings. ```objective-c [Dynatrace startupWithConfig:@{ kDTXApplicationID: @"YOUR_APPLICATION_ID", kDTXBeaconURL: @"https://your-environment.dynatrace.com/mbeacon", kDTXCrashReportingEnabled: @YES, kDTXLogLevel: @"INFO", kDTXAllowAnyCert: @NO, kDTXUserOptIn: @NO }]; ```