fix: correctly populate response_status (#7822)

Signed-off-by: Shivanshu Raj Shrivastava <shivanshu1333@gmail.com>
This commit is contained in:
Shivanshu Raj Shrivastava 2025-05-05 13:57:09 +05:30 committed by GitHub
parent b66af786e6
commit f4d029bd12
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 4 additions and 5 deletions

View File

@ -411,7 +411,7 @@ describe('API Monitoring Utils', () => {
const statusFilter = result.items.find(
(item) =>
item.key &&
item.key.key === SPAN_ATTRIBUTES.STATUS_CODE &&
item.key.key === SPAN_ATTRIBUTES.RESPONSE_STATUS_CODE &&
item.value === statusCode,
);
expect(statusFilter).toBeDefined();

View File

@ -13,7 +13,6 @@ export const VIEW_TYPES = {
// Span attribute keys - these are the source of truth for all attribute keys
export const SPAN_ATTRIBUTES = {
URL_PATH: 'http.url',
STATUS_CODE: 'status_code',
RESPONSE_STATUS_CODE: 'response_status_code',
SERVER_NAME: 'net.peer.name',
SERVER_PORT: 'net.peer.port',

View File

@ -1438,12 +1438,12 @@ export const getTopErrorsCoRelationQueryFilters = (
{
id: 'f6891e27',
key: {
key: 'status_code',
dataType: DataTypes.Float64,
key: 'response_status_code',
dataType: DataTypes.String,
type: '',
isColumn: true,
isJSON: false,
id: 'status_code--float64----true',
id: 'response_status_code--string----true',
},
op: '=',
value: statusCode,