API keys and configuration
The profiler configuration is generated from the account hierarchy in the portal. Create the objects in this order:
flowchart LR
Account["Customer account"] --> Application["Application"]
Application --> Environment["Environment"]
Application --> Profiler["Profiler"]
Environment --> Profiler
Profiler --> Config["Configuration block"]
Config --> App["Application settings"]
1. Create an application
An application represents the code base you want Reignite to analyze.
- Enter the source-control URL.
- Provide the main branch that represents production.
- Providing Application Insights access is recommended so ongoing analytics can be reviewed alongside traces.
2. Create an environment
An environment is a deployment target (for example Development, Staging or Production).
Enter a new environment name if one does not already exist.
3. Create a profiler
A profiler belongs to one application and one environment.
| Setting | Meaning | Suggested |
|---|---|---|
| Configuration Refresh Mins | How often a running agent re-reads its configuration. | 10 |
| Dump Wait Mins | Minimum time between memory dumps. | 60–720 |
| Trace Wait Mins | Minimum time between traces. | 60–120 |
4. Copy the configuration block
Open Configurations, select the profiler, and copy the generated block into your application's settings. The portal can generate a .NET/ASP.NET Core-shaped block, including the optional ASP.NET Core event counters.
The block carries the credentials:
| Key | Treat it as |
|---|---|
ProfilerID |
An identifier, not a secret. |
KeyID |
An identifier for the key. |
Secret |
A password. Never commit it, log it or paste it into a ticket. |
Environment |
The environment the agent reports under. |
5. Store the configuration safely
- Use your platform's secret store: App Service application settings, user secrets, Key Vault, or an equivalent.
- Keep the configuration out of source control.
- Give each environment its own profiler and credentials. Do not reuse a production secret in development.
6. Rotate a credential
- Create a replacement profiler (or replace the key in the portal, depending on the surface you have).
- Copy the new configuration block.
- Deploy the new secret to every instance.
- Confirm the new profiler is receiving metrics.
- Remove the old profiler or key.
Rotate after a suspected leak, when a team member leaves, and on a regular schedule.
Environment endpoints
The API endpoint depends on the environment. The generated environments table is the authority; the common values are:
| Environment | API |
|---|---|
| Local development | https://localhost:44332/api/v1/ |
| Integration | https://dev.api.reigniteperformance.com/api/v1/ |
| Preproduction | https://prep.api.reigniteperformance.com/api/v1/ |
| Production | https://api.reigniteperformance.com/api/v1/ |
Troubleshooting
| Symptom | Likely cause |
|---|---|
401 / 403 from the API |
KeyID/Secret mismatch, disabled profiler, or the wrong environment endpoint. |
| Metrics appear under the wrong environment | Environment in the configuration does not match the portal's environment name. |
| Configuration changes do not take effect | The refresh interval has not elapsed; wait or restart the agent. |
| No trace file appears | The threshold was never breached or the action has collection disabled. |