Request Logging — Request va response'larni monitoring qilish
Axios interceptorlari yordamida tarmoq so'rovlarini monitoring qilish, so'rov davomiyligini (duration) o'lchash, xavfsiz sanitizatsiya va development muhitida xatoliklarni kuzatish.
109-dars
Request Logging — Request va response'larni monitoring qilish
Katta hajmli frontend ilovalarini ishlab chiqish va qo'llab-quvvatlash jarayonida tarmoq so'rovlarini kuzatib borish (Request Logging) — bu xatoliklarni tezkor aniqlash, ishlash tezligini (Performance) o'lchash va ma'lumotlar oqimini nazorat qilishning eng samarali vositasidir.
Foydalanuvchi interfeysida biror nosozlik yoki sekinlashuv yuz berganda, brauzer konsolida aniq qaysi so'rov, qanday payload bilan yuborilgani, serverdan qanday status va javob qaytgani hamda jarayon necha millisekund davom etganini ko'rish muammoni daqiqalar ichida hal qilish imkonini beradi.
1. Axios Interceptor Yordamida Logging Mexanizmi
Axios'ning request va response interceptorlari so'rovning boshlanishi va tugashini to'liq nazorat qilish imkonini beradi:
- Request Interceptor: So'rov jo'natilishidan oldin uning boshlanish vaqtini (
performance.now()) maxsus metadata sifatida saqlab qo'yadi va so'rov tafsilotlarini konsolga chiqaradi. - Response Interceptor: Serverdan javob yetib kelganda yoki xatolik yuz berganda yakuniy vaqtni o'lchaydi va umumiy bajarilish davomiyligini (
duration) hisoblab chiqaradi.
flowchart LR
A["Komponent / Service"] --> B["Request Interceptor<br/>(startTime = performance.now())"]
B --> C["Serverga so'rov (HTTP)"]
C --> D["Response Interceptor<br/>(duration = now - startTime)"]
D --> E["Formatlangan Konsol Logi"]
2. Amaliyot: TypeScript Yordamida Professional Request Logger
Quyida so'rovlar davomiyligini hisoblovchi, guruhlangan chiroyli konsol chiqarishiga ega bo'lgan va asosiy maxfiy ma'lumotlarni tozalovchi logger interceptori keltirilgan:
// src/shared/api/interceptors/loggerInterceptor.ts
import { AxiosInstance, InternalAxiosRequestConfig, AxiosResponse, AxiosError } from 'axios';
// 1. Request config'ga vaqtni saqlash uchun maxsus metadata maydoni qo'shamiz
export interface LoggedRequestConfig extends InternalAxiosRequestConfig {
metadata?: {
startTime: number;
};
}
// 2. Maxfiy ma'lumotlarni konsolga chiqarmaslik uchun tozalovchi yordamchi funksiya
function sanitizeData(data: unknown): unknown {
if (!data) return data;
try {
const clone = typeof data === 'string' ? JSON.parse(data) : { ...(data as Record<string, unknown>) };
if ('password' in clone) clone.password = '***REDACTED***';
if ('token' in clone) clone.token = '***REDACTED***';
if ('refreshToken' in clone) clone.refreshToken = '***REDACTED***';
if ('secret' in clone) clone.secret = '***REDACTED***';
return clone;
} catch {
return data;
}
}
export const setupLoggerInterceptors = (axiosInstance: AxiosInstance): void => {
// REQUEST LOGGER
axiosInstance.interceptors.request.use(
(config: InternalAxiosRequestConfig) => {
const loggedConfig = config as LoggedRequestConfig;
// Faqat development muhitida ishlaydi
if (import.meta.env.DEV) {
loggedConfig.metadata = { startTime: performance.now() };
console.groupCollapsed(
`🚀 [API Request] ${config.method?.toUpperCase()} ${config.url}`
);
console.log('Headers:', config.headers);
if (config.params) {
console.log('Query Params:', config.params);
}
if (config.data) {
console.log('Payload:', sanitizeData(config.data));
}
console.groupEnd();
}
return loggedConfig;
},
(error: AxiosError) => {
if (import.meta.env.DEV) {
console.error('❌ [API Request Error]:', error.message);
}
return Promise.reject(error);
}
);
// RESPONSE LOGGER
axiosInstance.interceptors.response.use(
(response: AxiosResponse) => {
if (import.meta.env.DEV) {
const config = response.config as LoggedRequestConfig;
const startTime = config.metadata?.startTime || performance.now();
const duration = (performance.now() - startTime).toFixed(2);
console.groupCollapsed(
`✅ [API Response] ${response.config.method?.toUpperCase()} ${response.config.url} (${duration}ms)`
);
console.log('Status:', response.status);
console.log('Data:', response.data);
console.groupEnd();
}
return response;
},
(error: AxiosError) => {
if (import.meta.env.DEV) {
const config = error.config as LoggedRequestConfig | undefined;
const startTime = config?.metadata?.startTime || performance.now();
const duration = (performance.now() - startTime).toFixed(2);
console.groupCollapsed(
`❌ [API Error] ${error.config?.method?.toUpperCase()} ${error.config?.url} (${duration}ms)`
);
console.log('Status:', error.response?.status);
console.log('Message:', error.message);
console.log('Response Data:', error.response?.data);
console.groupEnd();
}
return Promise.reject(error);
}
);
};
[!TIP]
console.groupCollapsedfunksiyasi konsol to'lib ketishining oldini oladi. Dasturchi faqat o'ziga kerakli so'rov ustiga bosib, uning ichki tafsilotlarini kengaytirishi mumkin.
3. Client'ga Ulab Qo'yish
Yozgan logger interceptorimizni umumiy src/shared/api/client.ts faylida yaratilgan instansiyaga osongina ulaymiz:
// src/shared/api/client.ts
import axios, { AxiosInstance } from 'axios';
import { setupLoggerInterceptors } from './interceptors/loggerInterceptor';
export const apiClient: AxiosInstance = axios.create({
baseURL: import.meta.env.VITE_API_BASE_URL || 'https://api.mysite.com/v1',
timeout: 15000,
headers: {
'Content-Type': 'application/json',
},
});
// Logger interceptorlarini faollashtiramiz
setupLoggerInterceptors(apiClient);
4. Muhim Tavsiyalar va Xavfsizlik Qoidalari ⚠️
1. Production muhitida konsolga log yozishni o'chirish
Konsolga katta hajmdagi JSON obyektlarini chiqarish brauzer xotirasini band qiladi (Memory leak) va ilova ishlashini sekinlashtiradi. Eng xavflisi — foydalanuvchi konsolni ochganda uning shaxsiy ma'lumotlari ko'rinib qolishi mumkin. Shuning uchun barcha loglar import.meta.env.DEV sharti ostida bo'lishi shart.
2. Third-Party Monitoring (Tashqi Kuzatuv Tizimlari)
Production muhitida yuz bergan nosozliklarni tahlil qilish uchun konsolga yozish o'rniga, xatolik interceptori ichida xabarni Sentry, Datadog yoki LogRocket kabi ixtisoslashtirilgan xizmatlarga jo'natish zarur:
// Production error monitoring namunasi
if (!import.meta.env.DEV && error.response && error.response.status >= 500) {
// Sentry.captureException(error);
}
5. Taqqoslash: Development Logging vs Production Monitoring
| Mezon | Development Muhit (Dev Logging) | Production Muhit (Prod Monitoring) |
|---|---|---|
| Maqsad | Tezkor nosozliklarni aniqlash va tekshirish | Global xatolar va tizim barqarorligini tahlil qilish |
| Chiqarish joyi | Brauzer konsoli (console.groupCollapsed) |
Markaziy APM tizimlari (Sentry, Datadog) |
| Tafsilotlar | Barcha so'rovlar, headerlar, parametrlar, javoblar | Faqat kritik xatoliklar (4xx/5xx) va agregatlangan ko'rsatkichlar |
| Duration o'lchash | performance.now() orqali aniq millisekund |
Real User Monitoring (RUM) va P95/P99 latency |
| Xavfsizlik | Sanitizatsiya orqali maxfiy kalitlar maskalanadi | Qat'iy PII redaction, tokenlar to'liq o'chiriladi |
6. Xulosa
Request Logging interceptori — bu har bir dasturchining kundalik quroli bo'lib, quyidagi qulayliklarni taqdim etadi:
- Tarmoq so'rovining qancha vaqt olganini (
duration) aniq ko'rish; - Backend javobidagi xatolik xabarlari va status kodlarini chiroyli tarzda guruhlash;
- So'rov yuborilishidan oldin maxfiy qiymatlarni sanitizatsiya qilish;
- Ilovani production va development muhitlarida to'g'ri izolyatsiya qilish.