add post on native jfr

Author: roberttoyonaga

_data/authors.yaml

@@ -468,3 +468,9 @@ lthon:
   job_title: "Principal Software Engineer"
   twitter: "_Ladicek"
   bio: "Books. Software. Imagination..."
+rtoyonag:
+  name: "Robert Toyonaga"
+  email: "[email protected]"
+  emailhash: "4c720895d3cfe6ac32bd2fc326bfebab"
+  job_title: "Software Engineer"
+  bio: "Software Engineer, working at Red Hat on GraalVM Native Image."

_posts/2023-06-16-profile-and-monitor-in-native-mode.adoc

@@ -0,0 +1,10 @@
+---
+layout: post
+title: 'Use JFR to Profile and Monitor in Native Mode'
+date: 2023-07-21
+tags: development-tips native
+synopsis: Highlighting support for JFR in native mode.
+author: rtoyonag
+---
+
+Quarkus native applications offer many benefits such as even faster start-up time and low footprint. However, one major drawback is that such native binaries can be less observable. The good news is that you can still use JDK Flight Recorder (JFR) when running your Quarkus applications in native mode.  Native mode JFR is still limited compared to regular JFR in Java mode. However, major improvements have been made over the past couple years that make it a very powerful tool to profile and monitor your native executables. Check out these recent articles to find out more about how you can start using JFR in native mode: https://developers.redhat.com/articles/2023/06/13/how-monitor-quarkus-native-executables-jfr[How to monitor Quarkus native executables with JFR] and https://developers.redhat.com/articles/2023/06/13/improvements-native-image-jfr-support-graalvm-jdk-20[Improvements to Native Image JFR support in GraalVM for JDK 20]