When the default option values are returned, the list of dependent option values is not loaded
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 624
Description
### Environment
SaaS ([https://sentry.io/]())
### Version
*No response*
### Link
[https://c98416e79ee1.sentry.io/issues/3982627284]()
### DSN
[https://d077b91934f14ad088668f2ea48f363f@o1238224.ingest.sentry.io/4504733024583680]()
### Steps to Reproduce
1.Loading the issue page
2.Click integration application
3.Look at issue create for loading options that return default option values
### Expected Result
If an option has a default value, you do not need to click the option again to load the dependent option content
### Actual Result
If an option has a default value, you need to click the option again to load the dependent option

We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.
Examples**:**
* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs
---
**Candidate Metrics (add more below)**
* …
*(please also add ideas, questions or examples in comments)*
Contributor guide
Assessment
This issue has not been assessed yet.