Bug description
When selecting or filtering by environment in the Services page, the services API returns an invalid input error.
The failing API is:
GET https://xxxx/api/v2/services
Response:
{
"status": "error",
"error": {
"type": "invalid-input",
"code": "invalid_input",
"message": "Found 1 errors while parsing the search expression.",
"url": "https://signoz.io/docs/userguide/search-troubleshooting/#key-fieldname-not-found",
"errors": [
{
"message": "key `deployment.environment` not found"
}
]
}
}The page shows the error:
Found 1 errors while parsing the search expression.
It looks like the query generated by the Services page uses the field deployment.environment, but this key does not exist in the current data/schema.
Expected behavior
The Services page should load correctly after selecting an environment.
If deployment.environment is missing, SigNoz should either:
- handle the missing key gracefully;
- avoid generating a query with a non-existing field;
- show an empty result instead of returning an API error;
- or fallback to the correct environment/resource attribute if available.
How to reproduce
- Open the SigNoz UI.
- Go to the Services page.
- Select or filter by an environment.
- The page fails to load services and the API
/api/v2/services returns an error.
Version information
- Signoz version:
<please fill in>
- Browser version:
<please fill in>
- Your OS and version:
<please fill in>
- Your CPU Architecture(ARM/Intel):
<please fill in>
Additional context
The error message indicates that the search expression references a missing key:
key `deployment.environment` not found
This may happen when the telemetry data does not contain the deployment.environment resource attribute, but the Services page still generates a query using it.
Thank you for your bug report – we love squashing them!
Bug description
When selecting or filtering by environment in the Services page, the services API returns an invalid input error.
The failing API is:
Response:
{ "status": "error", "error": { "type": "invalid-input", "code": "invalid_input", "message": "Found 1 errors while parsing the search expression.", "url": "https://signoz.io/docs/userguide/search-troubleshooting/#key-fieldname-not-found", "errors": [ { "message": "key `deployment.environment` not found" } ] } }The page shows the error:
It looks like the query generated by the Services page uses the field
deployment.environment, but this key does not exist in the current data/schema.Expected behavior
The Services page should load correctly after selecting an environment.
If
deployment.environmentis missing, SigNoz should either:How to reproduce
/api/v2/servicesreturns an error.Version information
<please fill in><please fill in><please fill in><please fill in>Additional context
The error message indicates that the search expression references a missing key:
This may happen when the telemetry data does not contain the
deployment.environmentresource attribute, but the Services page still generates a query using it.Thank you for your bug report – we love squashing them!