# APM 기술 팁

[RUM Agent로 앱의 실제 사용자가 체감하는 성능 이슈를 모니터링하고 해결하는 방법 ](https://blog.naver.com/olpaemi/221976264938)

[파이썬(Python) 어플리케이션 로그와 APM 트레이스(Traces)를 연관 분석하는 방법 ](https://blog.naver.com/olpaemi/221973730638)\
[파이썬(Python) 어플의 구조화 로깅(Structured Logging) 구현하기 ](https://blog.naver.com/olpaemi/221967869387)

[MySQL의 통합적인 Observability(관측성) 확보하기 (로그+메트릭+성능데이터)](https://blog.naver.com/olpaemi/221965907947)

[인프라 시스템 메트릭을 통합하기 ](https://blog.naver.com/olpaemi/222003142311)

[쿠버네티스 환경의 자바 어플리케이션 모니터링하기 ](https://blog.naver.com/olpaemi/221788820388)

[아마존 EKS(Elastic Kubernetes Service)의 로그와 메트릭을 통합하기 ](https://blog.naver.com/olpaemi/222023215576)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://elastic-korea.gitbook.io/elastic-reference-box/apm/undefined.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.