Source identity
Records retain the identifiers needed for dependable comparison.
Product 02
Discover what exists in an environment.
LT Census Discovery is a built, provider-neutral engine with a separate runtime and trust boundary from LT Census Connect.
Launch scope
Environment → discovery → Census → Assets
Google Cloud
Projects and supported resources through Google Cloud Asset Inventory.
Separate product
A discovery product, not a Connect integration.
Discovery collects supported Google Cloud resources through Google Cloud Asset Inventory. It runs on infrastructure LTS operates outside Atlassian, then synchronises the result into Jira Service Management Assets.
Trust boundary
LTS operated infrastructure
Discovery is outside Atlassian’s Forge runtime. Security and architecture statements must account for that LTS operated boundary.
Keep the resource context visible.
Collection is only useful when teams can understand the records and the changes delivered to Assets.
Relationships
Supported relationships travel with resources into the Census model.
Execution history
Each run records what appeared, changed or went missing.
Illustrative run
See what changed.
New, changed and missing Google Cloud resources remain visible in the execution record.
Illustrative executionCompleted / 01:42
- Scanned
- 4,821
- Created
- 34
- Updated
- 127
- Unchanged
- 4,652
- Missing
- 8
+ gce-instance-4381
New resource discovered
~ production-cluster
machineType: n2-standard-4 → n2-standard-8
- legacy-project
Resource no longer discovered
LT Census
Evaluate LT Census Discovery.
Talk to us about supported Google Cloud resources and the LTS operated trust boundary ahead of Atlassian review.