Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (techsharer at outlook.com)
홈페이지
첨부 파일
 

Jennifersoft provides a trial promotion on its APM solution such as JENNIFER, PHP, and .NET in 2019 and shares the examples of their application.

We are promoting JENNIFER .NET APM without charge.

As of September 2, Jennifersoft starts offering JENNIFER promotion for those who want to try the software including an application operator, a developer or even for community. On top of PHP, we expand the range of promotion by adding .NET platform. If you are interested in experiencing the JENNIFER, please feel free to apply and use it free of charge for 3 months.


Please click below link to apply:

JENNIFER Promotion 2019 Indonesia
; http://bit.ly/JenniferINAPromotion2019

PENDAFTARAN FREE TRIAL APM JENNIFER
; https://www.iorad.com/player/1594390/PENDAFTARAN-FREE-TRIAL-APM-JENNIFER#trysteps-1

You are allowed to install and operate the software without charge from September 2 to November 30, 2019. If you have experienced performance related issues, now is a good chance to find what caused the problem and reinvent it by installing JENNIFER .NET APM.




Let me give you an example of .NET APM that has just been installed.

The webpage indicated above is a B2C website selling fashion items in Korea. Normally, the webpage does not show any issues, however, it radically becomes slow ever since it exports a promotional event. For this reason, the webpage administrator installed the JENNIFER .NET.

As you can see from the below, the webpage continues to respond to requests without any issues.

sample_net_mon_1.png

When you look at the “X-View” indicated at lower right corner of the screen, there are myriad of dots. These dots are marked on the display time of X-axis once a request is completed. The Y-axis indicates the length of time to process such request. Most of the time, dots are marked within 1 to 2 seconds (1,000ms to 2,000ms). Based on my experience, I can assure you that the webpage is one of the well-made websites, considering the fact that it is made without a monitoring tool.

Unfortunately, the webpage has been suffering from disorder due to a promotional event like below.

sample_net_mon_2.png

When you look at the Y-axis on X-View, lots of dots are marked on an area beyond 8 seconds (8,000ms). In other words, the response time becomes very slow as the webpage takes more than 8 seconds to complete the related requests. When I select the area where the response time becomes slow like a figure below,

[Figure: JENNIFER-APM solution]
jennifer_main_features_5.png

You can notice the time and the list of DB calling, and Web API calling that has occurred during the time of request. The figure indicates that it took tens of seconds at REST API calling for an outside company. Based on this result, the webpage company could come up with a solution to tackle the issue.




But the good thing is that this company was able to notice an error during the event period because the company at least conducted a basic system monitoring. Without the monitoring tool, the company could have not been noticed that they had a problem because the rapidly occurred requests by a push alarm normally end in such a short time. And it could have experienced decrease in sales and lost expense to prepare the promotion.

How do you feel now? Why don’t you find out yourself to see if you made your service reliably?




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]







[최초 등록일: ]
[최종 수정일: 9/27/2019]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer at outlook.com

비밀번호

댓글 작성자
 




... 31  32  33  34  35  36  37  38  39  40  41  42  43  [44]  45  ...
NoWriterDateCnt.TitleFile(s)
12530정성태2/4/202113061개발 환경 구성: 536. Wireshark + C#으로 확인하는 TCP 통신의 Receive Window
12529정성태2/4/202110144개발 환경 구성: 535. Wireshark + C#으로 확인하는 TCP 통신의 MIN RTO [1]
12528정성태2/1/20219551개발 환경 구성: 534. Wireshark + C#으로 확인하는 TCP 통신의 MSS(Maximum Segment Size) - 윈도우 환경
12527정성태2/1/20219768개발 환경 구성: 533. Wireshark + C#으로 확인하는 TCP 통신의 MSS(Maximum Segment Size) - 리눅스 환경파일 다운로드1
12526정성태2/1/20217627개발 환경 구성: 532. Azure Devops의 파이프라인 빌드 시 snk 파일 다루는 방법 - Secure file
12525정성태2/1/20217320개발 환경 구성: 531. Azure Devops - 파이프라인 실행 시 빌드 이벤트를 생략하는 방법
12524정성태1/31/20218395개발 환경 구성: 530. 기존 github 프로젝트를 Azure Devops의 빌드 Pipeline에 연결하는 방법 [1]
12523정성태1/31/20218420개발 환경 구성: 529. 기존 github 프로젝트를 Azure Devops의 Board에 연결하는 방법
12522정성태1/31/20219906개발 환경 구성: 528. 오라클 클라우드의 리눅스 VM - 9000 MTU Jumbo Frame 테스트
12521정성태1/31/20219922개발 환경 구성: 527. 이더넷(Ethernet) 환경의 TCP 통신에서 MSS(Maximum Segment Size) 확인 [1]
12520정성태1/30/20218424개발 환경 구성: 526. 오라클 클라우드의 VM에 ping ICMP 여는 방법
12519정성태1/30/20217522개발 환경 구성: 525. 오라클 클라우드의 VM을 외부에서 접근하기 위해 포트 여는 방법
12518정성태1/30/202124952Linux: 37. Ubuntu에 Wireshark 설치 [2]
12517정성태1/30/202112560Linux: 36. 윈도우 클라이언트에서 X2Go를 이용한 원격 리눅스의 GUI 접속 - 우분투 20.04
12516정성태1/29/20219214Windows: 188. Windows - TCP default template 설정 방법
12515정성태1/28/202110429웹: 41. Microsoft Edge - localhost에 대해 http 접근 시 무조건 https로 바뀌는 문제 [3]
12514정성태1/28/202110731.NET Framework: 1021. C# - 일렉트론 닷넷(Electron.NET) 소개 [1]파일 다운로드1
12513정성태1/28/20218740오류 유형: 698. electronize - User Profile 디렉터리에 공백 문자가 있는 경우 빌드가 실패하는 문제 [1]
12512정성태1/28/20218524오류 유형: 697. The program can't start because VCRUNTIME140.dll is missing from your computer. Try reinstalling the program to fix this problem.
12511정성태1/27/20218262Windows: 187. Windows - 도스 시절의 8.3 경로를 알아내는 방법
12510정성태1/27/20218666.NET Framework: 1020. .NET Core Kestrel 호스팅 - Razor 지원 추가 [1]파일 다운로드1
12509정성태1/27/20219613개발 환경 구성: 524. Jupyter Notebook에서 C#(F#, PowerShell) 언어 사용을 위한 환경 구성 [3]
12508정성태1/27/20218207개발 환경 구성: 523. Jupyter Notebook - Slide 플레이 버튼이 없는 경우
12507정성태1/26/20218332VS.NET IDE: 157. Visual Studio - Syntax Visualizer 메뉴가 없는 경우
12506정성태1/25/202111603.NET Framework: 1019. Microsoft.Tye 기본 사용법 소개 [1]
12505정성태1/23/20219376.NET Framework: 1018. .NET Core Kestrel 호스팅 - Web API 추가 [1]파일 다운로드1
... 31  32  33  34  35  36  37  38  39  40  41  42  43  [44]  45  ...