Software development lifecycle (SDLC) events

Latest Dynatrace
Reference
Published May 15, 2026

Software development lifecycle events are used to describe various stages throughout the lifecycle of a software component.

Such events can include, but are not limited to

CI/CD pipeline events
Task events emitted from a CI/CD pipeline
Task events occurring outside a CI/CD pipeline

Software development lifecycle events are mainly composed of the following namespaces

Artifact (artifact.* namespace)
Continuous Integration/Continuous Deployment (cicd.* namespace)
Deployment Attributes (deployment.* namespace)
VCS Repository (vcs.* namespace)

SDLC build finished task event

The SDLC task event "build finished" is generated when a build task is finished in the CI/CD system.

SDLC build finished task event fields

Attribute	Type	Description	Examples
`artifact.id`	string	experimentalThe identifier of the software artifact, typically the name of the artifact.	`carts-service`
`artifact.name`	string	experimentalThe human-readable name of the software artifact.	`Carts service`
`artifact.version`	string	experimentalThe version of the software artifact, typically in Semantic Versioning format.	`0.1.1`
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`duration`	duration	experimentalThe duration of the build task in nanoseconds.	`42`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the build task was finished.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC build finished task events.	`finished`
`event.type`	string	experimentalThe value must be set to `build` for any task event describing a build in the software development lifecycle.Tags: `permission`	`build`
`event.version`	string	experimentalThe version of the SDLC build finished task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the build task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`task.outcome`	string	experimentalOutcome of a task run.	`Success`; `Warning`; `Failure`; `Error`; `Skipped`; `Canceled`; `TimedOut`; `NotApplicable`
`task.queued.duration`	duration	experimentalHow long was the tasks queued before it was started, in nanoseconds.	`1234`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC build started task event

The SDLC task event "build started" is generated when a build task is started in the CI/CD system.

SDLC build started task event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `started` for SDLC build started task events.	`started`
`event.type`	string	experimentalThe value must be set to `build` for any task event describing a build in the software development lifecycle.Tags: `permission`	`build`
`event.version`	string	experimentalThe version of the SDLC build started task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the build task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC change finished task event

The SDLC task event "change finished" is generated when a change is closed in the version control system. A change task is the platform-agnostic term for a pull request in GitHub or a merge request in GitLab.

SDLC change finished task event fields

Attribute	Type	Description	Examples
`duration`	duration	experimentalHow long the change was open in the version control system, in nanoseconds.	`42`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the change was closed in the version control system.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC change finished task events.	`finished`
`event.type`	string	experimentalThe value must be set to `change` for any task event describing a change in the software development lifecycle.Tags: `permission`	`change`
`event.version`	string	experimentalThe version of the SDLC change finished task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the change was opened in the version control system.	`1649822520123123123`
`task.id`	string	experimentalThe internal identifier of the change tasks. It is typically unique per repository and generated by the version control system itself.	`871023010`
`task.name`	string	experimentalA human-readable name for a task.	`[Pull Request] docs: Update of Readme.md`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.change.id`	string	experimentalThe identifier of the change, for example, pull request ID or merge request ID. It is typically unique per repository and generated by the version control system itself.	`1234`
`vcs.change.state`	string	experimentalThe state of the change, for example, the state of a pull request or merge request.	`closed`; `merged`
`vcs.change.title`	string	experimentalThe human-readable title of the change, for example, pull request title or merge request title. ²	`docs: Update of Readme.md`
`vcs.change.url.full`	string	experimentalThe full URL to the change, for example, the full URL to the pull request or merge request.	`https://github.com/dynatrace-oss/terraform-provider-dynatrace/pull/20`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ³	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ⁴	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.ref.head.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ⁵	`my-branch-name`
`vcs.ref.head.revision`	string	experimentalThe revision in the repository. For Git, this is a synonym for a commit hash, whereas in SVN, it is a revision number. ⁶	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.name`	string	experimentalThe human-readable name of the repository. It should not include any additional identifiers like GitLab group or GitHub organization. ⁷	`dynatrace-configuration-as-code`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁸	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The value is similar to task.name.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

⁴

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁵

The head name refers to the current reference's name. For example, if main is currently checked out, the head name is main.

⁶

The head revision refers to the currently referenced revision.

⁷

Be aware that the repository name might clash with forked repositories.

⁸

For Git VCS, this should not include the .git URL suffix.

SDLC change started task event

The SDLC task event "change started" is generated when a change is openend in the version control system. A change task is the platform-agnostic term for a pull request in GitHub or a merge request in GitLab.

SDLC change started task event fields

Attribute	Type	Description	Examples
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `started` for SDLC change started task events.	`started`
`event.type`	string	experimentalThe value must be set to `change` for any task event describing a change in the software development lifecycle.Tags: `permission`	`change`
`event.version`	string	experimentalThe version of the SDLC change started task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the change was opened in the version control system.	`1649822520123123123`
`task.id`	string	experimentalThe internal identifier of the change tasks. It is typically unique per repository and generated by the version control system itself.	`871023010`
`task.name`	string	experimentalA human-readable name for a task.	`[Pull Request] docs: Update of Readme.md`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.change.id`	string	experimentalThe identifier of the change, for example, pull request ID or merge request ID. It is typically unique per repository and generated by the version control system itself.	`1234`
`vcs.change.state`	string	experimentalThe state of the change, for example, the state of a pull request or merge request.	`wip`; `open`; `reopened`
`vcs.change.title`	string	experimentalThe human-readable title of the change, for example, pull request title or merge request title. ²	`docs: Update of Readme.md`
`vcs.change.url.full`	string	experimentalThe full URL to the change, for example, the full URL to the pull request or merge request.	`https://github.com/dynatrace-oss/terraform-provider-dynatrace/pull/20`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ³	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ⁴	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.ref.head.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ⁵	`my-branch-name`
`vcs.ref.head.revision`	string	experimentalThe revision in the repository. For Git, this is a synonym for a commit hash, whereas in SVN, it is a revision number. ⁶	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.name`	string	experimentalThe human-readable name of the repository. It should not include any additional identifiers like GitLab group or GitHub organization. ⁷	`dynatrace-configuration-as-code`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁸	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The value is similar to task.name.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

⁴

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁵

The head name refers to the current reference's name. For example, if main is currently checked out, the head name is main.

⁶

The head revision refers to the currently referenced revision.

⁷

Be aware that the repository name might clash with forked repositories.

⁸

For Git VCS, this should not include the .git URL suffix.

SDLC deployment finished task event

The SDLC task event "deployment finished" is generated when a deployment task is finished.

SDLC deployment finished task event fields

Attribute	Type	Description	Examples
`cicd.deployment.id`	string	experimentalThe identifier of the deployment.	`1337`
`cicd.deployment.name`	string	experimentalThe name of the deployment.	`deploy frontend app`; `deploy cart service`
`cicd.deployment.namespace`	string	experimentalThe destination namespace where the deployment resource is created.	`default`
`cicd.deployment.release_stage`	string	experimentalThe name of the deployment environment, also known as deployment tier.	`development`; `staging`; `production`
`cicd.deployment.server.url.full`	string	experimentalThe deployment server URL.	`https://kubernetes.default.svc`
`cicd.deployment.service.id`	string	experimentalThe identifier of the service that is deployed.	`92ba59d6-379e-4ffd-a67e-d544a9c24dea`
`cicd.deployment.status`	string	experimentalThe status of the deployment.	`failed`; `succeeded`
`duration`	duration	experimentalHow long the deployment took.	`42`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the deployment task was finished.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`argocd`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC deployment finished task events.	`finished`
`event.type`	string	experimentalThe value must be set to `deployment` for any task event describing a deployment in the software development lifecycle.Tags: `permission`	`deployment`
`event.version`	string	experimentalThe version of the SDLC deployment finished task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the deployment task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`task.outcome`	string	experimentalThe outcome of the deployment task.	`Success`; `Error`; `Failure`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ²	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ³	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁴	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁴

For Git VCS, this should not include the .git URL suffix.

SDLC deployment started task event

The SDLC task event "deployment started" is generated when a deployment task is started.

SDLC deployment started task event fields

Attribute	Type	Description	Examples
`cicd.deployment.id`	string	experimentalThe identifier of the deployment.	`1337`
`cicd.deployment.name`	string	experimentalThe name of the deployment.	`deploy frontend app`; `deploy cart service`
`cicd.deployment.namespace`	string	experimentalThe destination namespace where the deployment resource is created.	`default`
`cicd.deployment.release_stage`	string	experimentalThe name of the deployment environment, also known as deployment tier.	`development`; `staging`; `production`
`cicd.deployment.server.url.full`	string	experimentalThe deployment server URL.	`https://kubernetes.default.svc`
`cicd.deployment.service.id`	string	experimentalThe identifier of the service that is deployed.	`92ba59d6-379e-4ffd-a67e-d544a9c24dea`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`argocd`
`event.status`	string	experimentalThe value must be set to `started` for SDLC deployment started task events.	`started`
`event.type`	string	experimentalThe value must be set to `deployment` for any task event describing a deployment in the software development lifecycle.Tags: `permission`	`deployment`
`event.version`	string	experimentalThe version of the SDLC deployment started task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the deployment task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ²	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ³	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁴	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁴

For Git VCS, this should not include the .git URL suffix.

SDLC pipeline run finished event

The SDLC pipeline event "run finished" is generated when a pipeline run is finished in the CI/CD system.

SDLC pipeline run finished event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.name`	string	experimentalThe human-readable name of the CI/CD pipeline.	`CI pipeline for main branch`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`cicd.pipeline.run.outcome`	string	experimentalThe outcome of one pipeline run.	`success`
`cicd.pipeline.run.queued.duration`	duration	experimentalHow long was the pipeline run queued before it was started, in nanoseconds.	`1234`
`cicd.pipeline.run.url.full`	string	experimentalThe URL pointing to one specific pipeline run.	`https://github.com/ACME/ACME-repo/actions/runs/9876`
`cicd.pipeline.url.full`	string	experimentalThe CI/CD pipeline's full URL.	`https://github.com/ACME/ACME-repo/actions/workflows/ci-build.yml`
`cicd.upstream_pipeline.id`	string	experimentalThe identifier of the upstream CI/CD pipeline. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline.	`12345`
`cicd.upstream_pipeline.run.id`	string	experimentalThe identifier of the upstream CI/CD pipeline run. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline run.	`1337`
`duration`	duration	experimentalThe duration of the pipeline run in nanoseconds.	`1234`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was finished.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `pipeline` for all pipeline events.	`pipeline`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC pipeline run finished events.	`finished`
`event.type`	string	experimentalThe value must be set to `run` for SDLC pipeline run finished events.Tags: `permission`	`run`
`event.version`	string	experimentalThe version of the SDLC pipeline run finished event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was started.	`1649822520123123123`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC pipeline run queued event

The SDLC pipeline event "run queued" is generated when a pipeline run is queued in the CI/CD system.

SDLC pipeline run queued event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.name`	string	experimentalThe human-readable name of the CI/CD pipeline.	`CI pipeline for main branch`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`cicd.pipeline.run.url.full`	string	experimentalThe URL pointing to one specific pipeline run.	`https://github.com/ACME/ACME-repo/actions/runs/9876`
`cicd.pipeline.url.full`	string	experimentalThe CI/CD pipeline's full URL.	`https://github.com/ACME/ACME-repo/actions/workflows/ci-build.yml`
`cicd.upstream_pipeline.id`	string	experimentalThe identifier of the upstream CI/CD pipeline. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline.	`12345`
`cicd.upstream_pipeline.run.id`	string	experimentalThe identifier of the upstream CI/CD pipeline run. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline run.	`1337`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `pipeline` for all pipeline events.	`pipeline`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `queued` for SDLC pipeline run queued events.	`queued`
`event.type`	string	experimentalThe value must be set to `run` for SDLC pipeline run queued events.Tags: `permission`	`run`
`event.version`	string	experimentalThe version of the SDLC pipeline run queued event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was queued.	`1649822520123123123`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC pipeline run started event

The SDLC pipeline event "run started" is generated when a pipeline run is started in the CI/CD system.

SDLC pipeline run started event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.name`	string	experimentalThe human-readable name of the CI/CD pipeline.	`CI pipeline for main branch`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`cicd.pipeline.run.queued.duration`	duration	experimentalHow long was the pipeline run queued before it was started, in nanoseconds.	`1234`
`cicd.pipeline.run.url.full`	string	experimentalThe URL pointing to one specific pipeline run.	`https://github.com/ACME/ACME-repo/actions/runs/9876`
`cicd.pipeline.url.full`	string	experimentalThe CI/CD pipeline's full URL.	`https://github.com/ACME/ACME-repo/actions/workflows/ci-build.yml`
`cicd.upstream_pipeline.id`	string	experimentalThe identifier of the upstream CI/CD pipeline. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline.	`12345`
`cicd.upstream_pipeline.run.id`	string	experimentalThe identifier of the upstream CI/CD pipeline run. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline run.	`1337`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `pipeline` for all pipeline events.	`pipeline`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `started` for SDLC pipeline run started events.	`started`
`event.type`	string	experimentalThe value must be set to `run` for SDLC pipeline run started events.Tags: `permission`	`run`
`event.version`	string	experimentalThe version of the SDLC pipeline run started event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was started.	`1649822520123123123`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC validation events

The SDLC validation events are generated when a validation is started or finished. This can happen in the context of a CI/CD system.

Query

Get all SDLC validation task events.

fetch events
| filter event.kind == "SDLC_EVENT" and event.category == "task" and event.type == "validation"

Get 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"

Get 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"

The common attributes listed in this section apply to both started and finished events, in addition to the specific attributes listed in the validation started and validation finished sections below.

For all validation events, event.kind must be SDLC_EVENT, event.category must be task, and event.type must be validation.

SDLC validation events fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe `cicd.pipeline.id` if the validation was triggered in the context of a CI/CD pipeline. Value is optional.	`12345`
`cicd.pipeline.run.id`	string	experimentalThe `cicd.pipeline.run.id` if the validation was triggered in the context of a CI/CD pipeline. Value is optional.	`9876`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC validation events.	`task`
`event.description`	string	experimentalValue is optional.	`This is a validation finished event`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.name`	string	experimentalValue is optional.	`Validation finished`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`dynatrace.site.reliability.guardian`
`event.status`	string	experimentalThe value must either be set to `started` for SDLC validation started task events or to `finished` for SDLC validation finished task events.	`finished`; `started`
`event.type`	string	experimentalThe value must be set to `validation` for any task event describing a validation in the Software Development Life Cycle.Tags: `permission`	`validation`
`event.version`	string	experimentalDescribes the version of the event.	`0.0.1`
`start_time`	timestamp	experimentalThe start time of the validation process. Value is optional.	`1649822520123123123`
`task.id`	string	experimentalValue is optional.	`123`
`task.name`	string	experimentalValue is optional.	`Validation for service-A during CI run of pipeline-B`
`task.outcome`	string	experimentalValue is optional.	`Success`; `Warning`; `Failure`; `Error`; `Skipped`; `Canceled`; `TimedOut`; `NotApplicable`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created.	`1649822520123123123`
`validation.from`	string	experimentalAn ISO 8601 compliant timestamp identifying the start of the validation timeframe. Value is optional. ²	`2024-10-09T20:00:12.199Z`
`validation.to`	string	experimentalAn ISO 8601 compliant timestamp identifying the end of the validation timeframe. Value is optional. ³	`2024-10-09T20:10:12.199Z`

Automatically and unconditionally set to value SDLC_EVENT.

This is not the start of the validation process, but the start of the timeframe if the underlying validation logic is timeframe-based, as would be the case for metrics.

This is not the end of the validation process, but the end of the timeframe if the underlying validation logic is timeframe-based, as would be the case for metrics.

SDLC task validation started event fields

This event type represents an SDLC validation started event. For a validation started event, event.status must be started.

Attribute	Type	Description	Examples
`event.status`	string	experimentalThe value must be set to `started` for SDLC validation started task events.	`started`

SDLC task validation finished event fields

This event type represents an SDLC validation finished event. For a validation finished event, event.status must be finished.

Attribute	Type	Description	Examples
`duration`	duration	experimentalThe duration of the validation process. This should be the time span between `start_time` and `end_time`. Value is optional.	`42`
`end_time`	timestamp	experimentalThe end time of the validation process. Value is optional.	`1649822520123123165`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC validation finished task events.	`finished`
`validation.at`	string	experimentalAn ISO 8601 compliant timestamp identifying the time when the validation process happened. Should be used to specify the timestamp when data had been retrieved, if the underlying validation logic would depend on that. In general, this timestamp should be greater than or equal to `start_time` and less than or equal to `end_time`. Value is optional. ¹	`2024-10-09T20:10:12.199Z`
`validation.result`	string	experimentalA text indicating the status of the finished validation.	`pass`; `warning`; `fail`; `info`; `error`

This timestamp or the timeframe determined by validation.to and validation.from should be set, depending on the use case. If there is no time-based component at all in the context of this validation, then all three fields are optional. Conversely, if the timeframe-based validation logic depends on data that might be sampled, then all three fields could be set.

Software development lifecycle (SDLC) events

Latest Dynatrace
Reference
Published May 15, 2026

Software development lifecycle events are used to describe various stages throughout the lifecycle of a software component.

Such events can include, but are not limited to

CI/CD pipeline events
Task events emitted from a CI/CD pipeline
Task events occurring outside a CI/CD pipeline

Software development lifecycle events are mainly composed of the following namespaces

Artifact (artifact.* namespace)
Continuous Integration/Continuous Deployment (cicd.* namespace)
Deployment Attributes (deployment.* namespace)
VCS Repository (vcs.* namespace)

SDLC build finished task event

The SDLC task event "build finished" is generated when a build task is finished in the CI/CD system.

SDLC build finished task event fields

Attribute	Type	Description	Examples
`artifact.id`	string	experimentalThe identifier of the software artifact, typically the name of the artifact.	`carts-service`
`artifact.name`	string	experimentalThe human-readable name of the software artifact.	`Carts service`
`artifact.version`	string	experimentalThe version of the software artifact, typically in Semantic Versioning format.	`0.1.1`
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`duration`	duration	experimentalThe duration of the build task in nanoseconds.	`42`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the build task was finished.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC build finished task events.	`finished`
`event.type`	string	experimentalThe value must be set to `build` for any task event describing a build in the software development lifecycle.Tags: `permission`	`build`
`event.version`	string	experimentalThe version of the SDLC build finished task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the build task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`task.outcome`	string	experimentalOutcome of a task run.	`Success`; `Warning`; `Failure`; `Error`; `Skipped`; `Canceled`; `TimedOut`; `NotApplicable`
`task.queued.duration`	duration	experimentalHow long was the tasks queued before it was started, in nanoseconds.	`1234`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC build started task event

The SDLC task event "build started" is generated when a build task is started in the CI/CD system.

SDLC build started task event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `started` for SDLC build started task events.	`started`
`event.type`	string	experimentalThe value must be set to `build` for any task event describing a build in the software development lifecycle.Tags: `permission`	`build`
`event.version`	string	experimentalThe version of the SDLC build started task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the build task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC change finished task event

SDLC change finished task event fields

Attribute	Type	Description	Examples
`duration`	duration	experimentalHow long the change was open in the version control system, in nanoseconds.	`42`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the change was closed in the version control system.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC change finished task events.	`finished`
`event.type`	string	experimentalThe value must be set to `change` for any task event describing a change in the software development lifecycle.Tags: `permission`	`change`
`event.version`	string	experimentalThe version of the SDLC change finished task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the change was opened in the version control system.	`1649822520123123123`
`task.id`	string	experimentalThe internal identifier of the change tasks. It is typically unique per repository and generated by the version control system itself.	`871023010`
`task.name`	string	experimentalA human-readable name for a task.	`[Pull Request] docs: Update of Readme.md`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.change.id`	string	experimentalThe identifier of the change, for example, pull request ID or merge request ID. It is typically unique per repository and generated by the version control system itself.	`1234`
`vcs.change.state`	string	experimentalThe state of the change, for example, the state of a pull request or merge request.	`closed`; `merged`
`vcs.change.title`	string	experimentalThe human-readable title of the change, for example, pull request title or merge request title. ²	`docs: Update of Readme.md`
`vcs.change.url.full`	string	experimentalThe full URL to the change, for example, the full URL to the pull request or merge request.	`https://github.com/dynatrace-oss/terraform-provider-dynatrace/pull/20`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ³	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ⁴	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.ref.head.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ⁵	`my-branch-name`
`vcs.ref.head.revision`	string	experimentalThe revision in the repository. For Git, this is a synonym for a commit hash, whereas in SVN, it is a revision number. ⁶	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.name`	string	experimentalThe human-readable name of the repository. It should not include any additional identifiers like GitLab group or GitHub organization. ⁷	`dynatrace-configuration-as-code`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁸	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The value is similar to task.name.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

⁴

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁵

The head name refers to the current reference's name. For example, if main is currently checked out, the head name is main.

⁶

The head revision refers to the currently referenced revision.

⁷

Be aware that the repository name might clash with forked repositories.

⁸

For Git VCS, this should not include the .git URL suffix.

SDLC change started task event

SDLC change started task event fields

Attribute	Type	Description	Examples
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `started` for SDLC change started task events.	`started`
`event.type`	string	experimentalThe value must be set to `change` for any task event describing a change in the software development lifecycle.Tags: `permission`	`change`
`event.version`	string	experimentalThe version of the SDLC change started task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the change was opened in the version control system.	`1649822520123123123`
`task.id`	string	experimentalThe internal identifier of the change tasks. It is typically unique per repository and generated by the version control system itself.	`871023010`
`task.name`	string	experimentalA human-readable name for a task.	`[Pull Request] docs: Update of Readme.md`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.change.id`	string	experimentalThe identifier of the change, for example, pull request ID or merge request ID. It is typically unique per repository and generated by the version control system itself.	`1234`
`vcs.change.state`	string	experimentalThe state of the change, for example, the state of a pull request or merge request.	`wip`; `open`; `reopened`
`vcs.change.title`	string	experimentalThe human-readable title of the change, for example, pull request title or merge request title. ²	`docs: Update of Readme.md`
`vcs.change.url.full`	string	experimentalThe full URL to the change, for example, the full URL to the pull request or merge request.	`https://github.com/dynatrace-oss/terraform-provider-dynatrace/pull/20`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ³	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ⁴	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.ref.head.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ⁵	`my-branch-name`
`vcs.ref.head.revision`	string	experimentalThe revision in the repository. For Git, this is a synonym for a commit hash, whereas in SVN, it is a revision number. ⁶	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.name`	string	experimentalThe human-readable name of the repository. It should not include any additional identifiers like GitLab group or GitHub organization. ⁷	`dynatrace-configuration-as-code`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁸	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The value is similar to task.name.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

⁴

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁵

The head name refers to the current reference's name. For example, if main is currently checked out, the head name is main.

⁶

The head revision refers to the currently referenced revision.

⁷

Be aware that the repository name might clash with forked repositories.

⁸

For Git VCS, this should not include the .git URL suffix.

SDLC deployment finished task event

The SDLC task event "deployment finished" is generated when a deployment task is finished.

SDLC deployment finished task event fields

Attribute	Type	Description	Examples
`cicd.deployment.id`	string	experimentalThe identifier of the deployment.	`1337`
`cicd.deployment.name`	string	experimentalThe name of the deployment.	`deploy frontend app`; `deploy cart service`
`cicd.deployment.namespace`	string	experimentalThe destination namespace where the deployment resource is created.	`default`
`cicd.deployment.release_stage`	string	experimentalThe name of the deployment environment, also known as deployment tier.	`development`; `staging`; `production`
`cicd.deployment.server.url.full`	string	experimentalThe deployment server URL.	`https://kubernetes.default.svc`
`cicd.deployment.service.id`	string	experimentalThe identifier of the service that is deployed.	`92ba59d6-379e-4ffd-a67e-d544a9c24dea`
`cicd.deployment.status`	string	experimentalThe status of the deployment.	`failed`; `succeeded`
`duration`	duration	experimentalHow long the deployment took.	`42`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the deployment task was finished.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`argocd`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC deployment finished task events.	`finished`
`event.type`	string	experimentalThe value must be set to `deployment` for any task event describing a deployment in the software development lifecycle.Tags: `permission`	`deployment`
`event.version`	string	experimentalThe version of the SDLC deployment finished task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the deployment task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`task.outcome`	string	experimentalThe outcome of the deployment task.	`Success`; `Error`; `Failure`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ²	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ³	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁴	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁴

For Git VCS, this should not include the .git URL suffix.

SDLC deployment started task event

The SDLC task event "deployment started" is generated when a deployment task is started.

SDLC deployment started task event fields

Attribute	Type	Description	Examples
`cicd.deployment.id`	string	experimentalThe identifier of the deployment.	`1337`
`cicd.deployment.name`	string	experimentalThe name of the deployment.	`deploy frontend app`; `deploy cart service`
`cicd.deployment.namespace`	string	experimentalThe destination namespace where the deployment resource is created.	`default`
`cicd.deployment.release_stage`	string	experimentalThe name of the deployment environment, also known as deployment tier.	`development`; `staging`; `production`
`cicd.deployment.server.url.full`	string	experimentalThe deployment server URL.	`https://kubernetes.default.svc`
`cicd.deployment.service.id`	string	experimentalThe identifier of the service that is deployed.	`92ba59d6-379e-4ffd-a67e-d544a9c24dea`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC task events.	`task`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`argocd`
`event.status`	string	experimentalThe value must be set to `started` for SDLC deployment started task events.	`started`
`event.type`	string	experimentalThe value must be set to `deployment` for any task event describing a deployment in the software development lifecycle.Tags: `permission`	`deployment`
`event.version`	string	experimentalThe version of the SDLC deployment started task event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the deployment task was started.	`1649822520123123123`
`task.id`	string	experimentalThe unique task identifier.	`123`
`task.name`	string	experimentalA human-readable name for a task.	`CI build my-service`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`
`vcs.ref.base.name`	string	experimentalThe name of the reference in the repository. This can be a branch name or a tag name. ²	`my-branch-name`
`vcs.ref.base.revision`	string	experimentalThe revision in the repository. For Git this is a synonym for a commit hash, whereas in SVN it is a revision number. ³	`d4322ab6cba38d21ad83c9de304a6a214ecf2cdc`; `main`; `1337`
`vcs.repository.url.full`	string	experimentalThe repository's full URL. ⁴	`https://github.com/dynatrace-oss/terraform-provider-dynatrace`

Automatically and unconditionally set to value SDLC_EVENT.

The base name refers to the starting point of a change. For example, if a feature branch was created from main, main is the base reference of type branch.

The base revision refers to the starting revision of a change. For example, if a branch was created from a certain commit, this commit is the base revision.

⁴

For Git VCS, this should not include the .git URL suffix.

SDLC pipeline run finished event

The SDLC pipeline event "run finished" is generated when a pipeline run is finished in the CI/CD system.

SDLC pipeline run finished event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.name`	string	experimentalThe human-readable name of the CI/CD pipeline.	`CI pipeline for main branch`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`cicd.pipeline.run.outcome`	string	experimentalThe outcome of one pipeline run.	`success`
`cicd.pipeline.run.queued.duration`	duration	experimentalHow long was the pipeline run queued before it was started, in nanoseconds.	`1234`
`cicd.pipeline.run.url.full`	string	experimentalThe URL pointing to one specific pipeline run.	`https://github.com/ACME/ACME-repo/actions/runs/9876`
`cicd.pipeline.url.full`	string	experimentalThe CI/CD pipeline's full URL.	`https://github.com/ACME/ACME-repo/actions/workflows/ci-build.yml`
`cicd.upstream_pipeline.id`	string	experimentalThe identifier of the upstream CI/CD pipeline. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline.	`12345`
`cicd.upstream_pipeline.run.id`	string	experimentalThe identifier of the upstream CI/CD pipeline run. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline run.	`1337`
`duration`	duration	experimentalThe duration of the pipeline run in nanoseconds.	`1234`
`end_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was finished.	`1649822520123123165`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `pipeline` for all pipeline events.	`pipeline`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC pipeline run finished events.	`finished`
`event.type`	string	experimentalThe value must be set to `run` for SDLC pipeline run finished events.Tags: `permission`	`run`
`event.version`	string	experimentalThe version of the SDLC pipeline run finished event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was started.	`1649822520123123123`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC pipeline run queued event

The SDLC pipeline event "run queued" is generated when a pipeline run is queued in the CI/CD system.

SDLC pipeline run queued event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.name`	string	experimentalThe human-readable name of the CI/CD pipeline.	`CI pipeline for main branch`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`cicd.pipeline.run.url.full`	string	experimentalThe URL pointing to one specific pipeline run.	`https://github.com/ACME/ACME-repo/actions/runs/9876`
`cicd.pipeline.url.full`	string	experimentalThe CI/CD pipeline's full URL.	`https://github.com/ACME/ACME-repo/actions/workflows/ci-build.yml`
`cicd.upstream_pipeline.id`	string	experimentalThe identifier of the upstream CI/CD pipeline. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline.	`12345`
`cicd.upstream_pipeline.run.id`	string	experimentalThe identifier of the upstream CI/CD pipeline run. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline run.	`1337`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `pipeline` for all pipeline events.	`pipeline`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `queued` for SDLC pipeline run queued events.	`queued`
`event.type`	string	experimentalThe value must be set to `run` for SDLC pipeline run queued events.Tags: `permission`	`run`
`event.version`	string	experimentalThe version of the SDLC pipeline run queued event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was queued.	`1649822520123123123`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC pipeline run started event

The SDLC pipeline event "run started" is generated when a pipeline run is started in the CI/CD system.

SDLC pipeline run started event fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe CI/CD pipeline's identifier, which is unique within one CI/CD system.	`12345`
`cicd.pipeline.name`	string	experimentalThe human-readable name of the CI/CD pipeline.	`CI pipeline for main branch`
`cicd.pipeline.run.id`	string	experimentalAn identifier for a pipeline run, which is unique within one CI/CD system.	`9876`
`cicd.pipeline.run.queued.duration`	duration	experimentalHow long was the pipeline run queued before it was started, in nanoseconds.	`1234`
`cicd.pipeline.run.url.full`	string	experimentalThe URL pointing to one specific pipeline run.	`https://github.com/ACME/ACME-repo/actions/runs/9876`
`cicd.pipeline.url.full`	string	experimentalThe CI/CD pipeline's full URL.	`https://github.com/ACME/ACME-repo/actions/workflows/ci-build.yml`
`cicd.upstream_pipeline.id`	string	experimentalThe identifier of the upstream CI/CD pipeline. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline.	`12345`
`cicd.upstream_pipeline.run.id`	string	experimentalThe identifier of the upstream CI/CD pipeline run. If a pipeline run was triggered by another pipeline, this attribute is used to reference the triggering pipeline run.	`1337`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `pipeline` for all pipeline events.	`pipeline`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`github.com`
`event.status`	string	experimentalThe value must be set to `started` for SDLC pipeline run started events.	`started`
`event.type`	string	experimentalThe value must be set to `run` for SDLC pipeline run started events.Tags: `permission`	`run`
`event.version`	string	experimentalThe version of the SDLC pipeline run started event.	`0.1.0`
`start_time`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the pipeline run was started.	`1649822520123123123`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created.	`1649822520123123123`

Automatically and unconditionally set to value SDLC_EVENT.

SDLC validation events

The SDLC validation events are generated when a validation is started or finished. This can happen in the context of a CI/CD system.

Query

Get all SDLC validation task events.

fetch events
| filter event.kind == "SDLC_EVENT" and event.category == "task" and event.type == "validation"

Get 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"

Get 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"

For all validation events, event.kind must be SDLC_EVENT, event.category must be task, and event.type must be validation.

SDLC validation events fields

Attribute	Type	Description	Examples
`cicd.pipeline.id`	string	experimentalThe `cicd.pipeline.id` if the validation was triggered in the context of a CI/CD pipeline. Value is optional.	`12345`
`cicd.pipeline.run.id`	string	experimentalThe `cicd.pipeline.run.id` if the validation was triggered in the context of a CI/CD pipeline. Value is optional.	`9876`
`event.category`	string	experimentalDescribes the SDLC event's category, which must be set to `task` for SDLC validation events.	`task`
`event.description`	string	experimentalValue is optional.	`This is a validation finished event`
`event.id`	string	experimentalUnique identifier string of an event; is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.kind`	string	experimentalGives 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. ¹Tags: `permission`	`SDLC_EVENT`
`event.name`	string	experimentalValue is optional.	`Validation finished`
`event.provider`	string	experimentalSource of the event, for example, the name of the component or system that generated the event.Tags: `permission`	`dynatrace.site.reliability.guardian`
`event.status`	string	experimentalThe value must either be set to `started` for SDLC validation started task events or to `finished` for SDLC validation finished task events.	`finished`; `started`
`event.type`	string	experimentalThe value must be set to `validation` for any task event describing a validation in the Software Development Life Cycle.Tags: `permission`	`validation`
`event.version`	string	experimentalDescribes the version of the event.	`0.0.1`
`start_time`	timestamp	experimentalThe start time of the validation process. Value is optional.	`1649822520123123123`
`task.id`	string	experimentalValue is optional.	`123`
`task.name`	string	experimentalValue is optional.	`Validation for service-A during CI run of pipeline-B`
`task.outcome`	string	experimentalValue is optional.	`Success`; `Warning`; `Failure`; `Error`; `Skipped`; `Canceled`; `TimedOut`; `NotApplicable`
`timestamp`	timestamp	experimentalThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created.	`1649822520123123123`
`validation.from`	string	experimentalAn ISO 8601 compliant timestamp identifying the start of the validation timeframe. Value is optional. ²	`2024-10-09T20:00:12.199Z`
`validation.to`	string	experimentalAn ISO 8601 compliant timestamp identifying the end of the validation timeframe. Value is optional. ³	`2024-10-09T20:10:12.199Z`

Automatically and unconditionally set to value SDLC_EVENT.

This is not the start of the validation process, but the start of the timeframe if the underlying validation logic is timeframe-based, as would be the case for metrics.

This is not the end of the validation process, but the end of the timeframe if the underlying validation logic is timeframe-based, as would be the case for metrics.

SDLC task validation started event fields

This event type represents an SDLC validation started event. For a validation started event, event.status must be started.

Attribute	Type	Description	Examples
`event.status`	string	experimentalThe value must be set to `started` for SDLC validation started task events.	`started`

SDLC task validation finished event fields

This event type represents an SDLC validation finished event. For a validation finished event, event.status must be finished.

Attribute	Type	Description	Examples
`duration`	duration	experimentalThe duration of the validation process. This should be the time span between `start_time` and `end_time`. Value is optional.	`42`
`end_time`	timestamp	experimentalThe end time of the validation process. Value is optional.	`1649822520123123165`
`event.status`	string	experimentalThe value must be set to `finished` for SDLC validation finished task events.	`finished`
`validation.at`	string	experimentalAn ISO 8601 compliant timestamp identifying the time when the validation process happened. Should be used to specify the timestamp when data had been retrieved, if the underlying validation logic would depend on that. In general, this timestamp should be greater than or equal to `start_time` and less than or equal to `end_time`. Value is optional. ¹	`2024-10-09T20:10:12.199Z`
`validation.result`	string	experimentalA text indicating the status of the finished validation.	`pass`; `warning`; `fail`; `info`; `error`