{"id":54191,"date":"2025-11-25T17:26:47","date_gmt":"2025-11-25T17:26:47","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=54191"},"modified":"2026-02-21T08:29:11","modified_gmt":"2026-02-21T08:29:11","slug":"dotnet-gcdump-lightweight-net-memory-profiling-tool-advanced-tutorial","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/dotnet-gcdump-lightweight-net-memory-profiling-tool-advanced-tutorial\/","title":{"rendered":"dotnet-gcdump \u2014 lightweight .NET memory profiling tool Advanced Tutorial"},"content":{"rendered":"\n
\n\n\n\n

<\/h1>\n\n\n\n
\n\n\n\n

1. What is dotnet-gcdump<\/code>?<\/strong><\/h1>\n\n\n\n

dotnet-gcdump<\/code> is a lightweight .NET memory profiling tool<\/strong> that collects GC (Garbage Collector) heap dumps<\/strong> with minimal performance overhead<\/strong>.<\/p>\n\n\n\n

It gives you:<\/p>\n\n\n\n

    \n
  • Managed heap snapshot<\/strong><\/li>\n\n\n\n
  • Objects allocation information<\/strong><\/li>\n\n\n\n
  • Object types, sizes, counts<\/strong><\/li>\n\n\n\n
  • Reference trees (roots, retainers)<\/strong><\/li>\n\n\n\n
  • Memory pressure analysis<\/strong><\/li>\n<\/ul>\n\n\n\n

    It is part of the .NET diagnostics toolset along with:<\/p>\n\n\n\n

      \n
    • dotnet-counters<\/code><\/li>\n\n\n\n
    • dotnet-trace<\/code><\/li>\n\n\n\n
    • dotnet-dump<\/code><\/li>\n\n\n\n
    • dotnet-monitor<\/code><\/li>\n<\/ul>\n\n\n\n

      \ud83d\udca1 Think of dotnet-gcdump as the “lightest way” to understand memory usage without pausing\/stopping the app<\/strong>.<\/p>\n\n\n\n

      \n\n\n\n

      2. Why Use dotnet-gcdump<\/code>?<\/strong><\/h1>\n\n\n\n

      \u2714 Extremely low overhead<\/h3>\n\n\n\n

      You can capture memory dumps on live production apps with almost zero impact<\/strong>.<\/p>\n\n\n\n

      \u2714 Perfect for memory leak detection<\/h3>\n\n\n\n

      It shows object types and counts to help identify:<\/p>\n\n\n\n

        \n
      • Memory leaks<\/li>\n\n\n\n
      • Excessive retained objects<\/li>\n\n\n\n
      • High fragmentation<\/li>\n\n\n\n
      • Objects not being freed<\/li>\n<\/ul>\n\n\n\n

        \u2714 Works cross-platform<\/h3>\n\n\n\n

        Runs on Windows, Linux, and macOS<\/strong>.<\/p>\n\n\n\n

        \u2714 Great for comparing memory snapshots over time<\/h3>\n\n\n\n

        Useful for before\/after deployment analysis.<\/p>\n\n\n\n

        \n\n\n\n

        3. When to Use dotnet-gcdump<\/code>?<\/strong><\/h1>\n\n\n\n

        Use it whenever you see:<\/p>\n\n\n\n

        \ud83d\udfe1 Increasing memory usage in Production<\/strong><\/h3>\n\n\n\n
          \n
        • Memory slowly goes up \u2192 leak<\/li>\n\n\n\n
        • Too many pinned objects \u2192 fragmentation<\/li>\n\n\n\n
        • Large object heap (LOH) too high<\/li>\n<\/ul>\n\n\n\n

          \ud83d\udfe1 GC performance issues<\/strong><\/h3>\n\n\n\n
            \n
          • High GC frequency<\/li>\n\n\n\n
          • High fragmentation<\/li>\n\n\n\n
          • Slowness or pauses<\/li>\n<\/ul>\n\n\n\n

            \ud83d\udfe1 Investigate specific request memory spikes<\/strong><\/h3>\n\n\n\n

            Take a snapshot:<\/p>\n\n\n

            Before request \u2192 gcdump \u2192 After request\n<\/code><\/span><\/pre>\n\n\n
            \ud83d\udfe1 Compare two environment behaviors<\/strong><\/h3>\n\n\n\n
              \n
            • Prod vs Stage<\/li>\n\n\n\n
            • .NET version upgrade comparison<\/li>\n\n\n\n
            • New features memory comparison<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n
              4. How to Install dotnet-gcdump<\/code><\/strong><\/h1>\n\n\n
              dotnet tool install --global<\/span> dotnet-gcdump\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
              Verify:<\/p>\n\n\n
              dotnet-gcdump --version\n<\/code><\/span><\/pre>\n\n\n
              \n\n\n\n
              5. How to Use dotnet-gcdump<\/code><\/strong><\/h1>\n\n\n\n
              A. Find your running .NET process<\/strong><\/h2>\n\n\n
              dotnet-gcdump ps\n<\/code><\/span><\/pre>\n\n\n
              Example output:<\/p>\n\n\n
                5120   MyApp<\/span>.Api<\/span>\n  5566   Orders<\/span>.Web<\/span>\n  7788   BackgroundWorker<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              B. Collect a GC dump from a running process<\/strong><\/h2>\n\n\n
              dotnet-gcdump collect --process-id 5566\n<\/code><\/span><\/pre>\n\n\n
              You will get:<\/p>\n\n\n
              Writing<\/span> gcdump<\/span> to<\/span> MyApp_20261125_142410<\/span>.gcdump<\/span>\nComplete<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              C. Collect a dump from a process that will start now<\/strong><\/h2>\n\n\n
              dotnet-gcdump<\/span> collect<\/span> --<\/span> myapp<\/span>.exe<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              D. Specify output file<\/strong><\/h2>\n\n\n
              dotnet-gcdump collect --process-id 5566 --output \/tmp\/myapp-leak.gcdump\n<\/code><\/span><\/pre>\n\n\n
              \n\n\n\n
              6. How to Analyze a GCDump<\/strong><\/h1>\n\n\n\n
              \u2714 Best tool: PerfView<\/strong><\/h2>\n\n\n\n
              (Microsoft official memory analysis tool)<\/p>\n\n\n\n
              Open PerfView \u2192
              File \u2192 Open \u2192 .gcdump file<\/strong><\/p>\n\n\n\n
              You will see:<\/p>\n\n\n\n
              You can inspect:<\/p>\n\n\n\n
              \u2714 Heap Size<\/h3>\n\n\n\n
              \u2714 Object Types<\/h3>\n\n\n\n
              \u2714 Count & Size<\/h3>\n\n\n\n
              \u2714 Roots<\/h3>\n\n\n\n
              \u2714 Retention Graph<\/h3>\n\n\n\n
              \u2714 Diff View (compare two dumps)<\/h3>\n\n\n\n
              \n\n\n\n
              7. Important Metrics in a GC Dump<\/strong><\/h1>\n\n\n\n
              Metric<\/th>Meaning<\/th>Why Important<\/th><\/tr><\/thead>
              Total Heap Size<\/strong><\/td>Total memory used by managed heap<\/td>Detect memory bloat<\/td><\/tr>
              Gen 0\/1\/2 Size<\/strong><\/td>Memory per generation<\/td>Shows GC pressure<\/td><\/tr>
              LOH (Large Object Heap)<\/strong><\/td>Objects > 85 KB<\/td>High LOH = fragmentation risk<\/td><\/tr>
              Pinned Objects<\/strong><\/td>Objects fixed in memory<\/td>Affects GC performance<\/td><\/tr>
              Object Count<\/strong><\/td>How many objects of each type<\/td>Shows leaks (e.g., growing list)<\/td><\/tr>
              Retainers \/ Roots<\/strong><\/td>What is holding objects alive<\/td>Critical for leak detection<\/td><\/tr>
              Diff View<\/strong><\/td>Compare two snapshots<\/td>Identifies what grew<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
              \n\n\n\n
              8. Common Memory Issues Detected via GCDump<\/strong><\/h1>\n\n\n\n
              \ud83d\udd25 Memory Leaks<\/strong><\/h3>\n\n\n\n
                \n
              • Singleton holding references<\/li>\n\n\n\n
              • Event handlers not unsubscribed<\/li>\n\n\n\n
              • Static lists growing<\/li>\n<\/ul>\n\n\n\n
                \ud83d\udd25 Large Object Heap Pressure<\/strong><\/h3>\n\n\n\n
                  \n
                • Large arrays<\/li>\n\n\n\n
                • Images \/ byte[]<\/li>\n\n\n\n
                • Serialization buffers<\/li>\n<\/ul>\n\n\n\n
                  \ud83d\udd25 Excessive Allocation<\/strong><\/h3>\n\n\n\n
                    \n
                  • Chatty LINQ<\/li>\n\n\n\n
                  • Unoptimized JSON serialization<\/li>\n\n\n\n
                  • Inefficient loops<\/li>\n<\/ul>\n\n\n\n
                    \ud83d\udd25 Pinned Objects Issues<\/strong><\/h3>\n\n\n\n
                      \n
                    • GPU buffers<\/li>\n\n\n\n
                    • Unsafe code<\/li>\n\n\n\n
                    • Interop<\/li>\n<\/ul>\n\n\n\n
                      \n\n\n\n
                      9. Advanced Usage<\/strong><\/h1>\n\n\n\n
                      A. Collect after forcing GC (for cleaner dump)<\/h2>\n\n\n
                      dotnet-gcdump collect --process-id 5566 --gc-collect\n<\/code><\/span><\/pre>\n\n\n
                      B. Collect for a process name (not PID)<\/h2>\n\n\n
                      dotnet-gcdump<\/span> collect<\/span> --name<\/span> Orders<\/span>.Api<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \n\n\n\n
                      10. Advantages of dotnet-gcdump<\/code><\/strong><\/h1>\n\n\n\n
                      Feature<\/th>Benefit<\/th><\/tr><\/thead>
                      Lightweight<\/td>Safe in production<\/td><\/tr>
                      Zero-impact on performance<\/td>Unlike full dump<\/td><\/tr>
                      Easy to automate<\/td>CI, cron, scripts<\/td><\/tr>
                      Cross-platform<\/td>Works everywhere<\/td><\/tr>
                      Works with PerfView<\/td>Powerful analysis UI<\/td><\/tr>
                      Can compare snapshots<\/td>Detect leaks precisely<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                      \n\n\n\n
                      11. Limitations of dotnet-gcdump<\/code><\/strong><\/h1>\n\n\n\n
                      Limitation<\/th>Notes<\/th><\/tr><\/thead>
                      Cannot debug code execution<\/td>Use dotnet-trace<\/td><\/tr>
                      Only managed heap<\/td>No native memory<\/td><\/tr>
                      Limited call stacks<\/td>Not full session trace<\/td><\/tr>
                      No CPU profiling<\/td>Use dotnet-trace<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                      \n\n\n\n
                      12. Best Practices<\/strong><\/h1>\n\n\n\n
                      \u2b50 Capture multiple dumps<\/h3>\n\n\n\n
                      Before, during, after load test.<\/p>\n\n\n\n
                      \u2b50 Always analyze with PerfView<\/h3>\n\n\n\n
                      It is the official recommended tool.<\/p>\n\n\n\n
                      \u2b50 Automate weekly GC dumps in production<\/h3>\n\n\n\n
                      Useful for long-running apps.<\/p>\n\n\n\n
                      \u2b50 Combine with dotnet-counters<\/code><\/h3>\n\n\n\n
                      To monitor GC in real-time.<\/p>\n\n\n\n
                      \n\n\n\n
                      <\/p>\n\n\n\n
                      \n\n\n\n
                      \u2705 1. Basic Example \u2014 Capture a GC Dump from a Running Process<\/strong><\/h1>\n\n\n\n
                      Step 1 \u2014 List running .NET processes<\/h3>\n\n\n
                      dotnet-gcdump ps\n<\/code><\/span><\/pre>\n\n\n
                      Example Output:<\/strong><\/p>\n\n\n
                        5120   Orders<\/span>.Api<\/span>\n  5566   LoginService<\/span>\n  7788   BackgroundWorker<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \n\n\n\n
                      Step 2 \u2014 Capture a GC dump from PID 5120<\/h3>\n\n\n
                      dotnet-gcdump collect --process-id 5120\n<\/code><\/span><\/pre>\n\n\n
                      Output Example:<\/strong><\/p>\n\n\n
                      Writing<\/span> gcdump<\/span> to<\/span> OrdersApi_20261125_141800<\/span>.gcdump<\/span>...\nComplete<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \ud83d\udc49 This creates a file like:<\/p>\n\n\n
                      OrdersApi_20261125_141800<\/span>.gcdump<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \n\n\n\n
                      \u2705 2. Example \u2014 Capture Dump of a Process by Name<\/strong><\/h1>\n\n\n\n
                      If you don\u2019t want to use PID:<\/p>\n\n\n
                      dotnet-gcdump<\/span> collect<\/span> --name<\/span> Orders<\/span>.Api<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Output:<\/p>\n\n\n
                      Found process 'Orders.Api'<\/span> (PID 5120<\/span>)\nWriting gcdump...\nComplete\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \n\n\n\n
                      \u2705 3. Example \u2014 Capture Dump and Save to Custom Path<\/strong><\/h1>\n\n\n
                      dotnet-gcdump collect \n  --process-id 5566 \n  --output \/logs\/memory\/Leak_5566_2PM.gcdump\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      \u2705 4. Example \u2014 Collect After Forcing a Full GC<\/strong><\/h1>\n\n\n\n
                      Useful when you want a clean snapshot:<\/p>\n\n\n
                      dotnet-gcdump collect --process-id 5566 --gc-collect\n<\/code><\/span><\/pre>\n\n\n
                      Output:<\/p>\n\n\n
                      Forcing full garbage collection...\nDumping managed heap...\nSuccess\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      \u2705 5. Example \u2014 Capture GCDump When Running a Command<\/strong><\/h1>\n\n\n\n
                      Run your app and immediately collect:<\/p>\n\n\n
                      dotnet-gcdump<\/span> collect<\/span> --<\/span> dotnet<\/span> run<\/span> --project<\/span> MyApp<\/span>.Api<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      This starts MyApp.Api<\/code>, collects dump, and exits.<\/p>\n\n\n\n
                      \n\n\n\n
                      \u2705 6. Example \u2014 Compare Two GCDumps (using PerfView)<\/strong><\/h1>\n\n\n\n
                        \n
                      1. Take two dumps: dotnet-gcdump collect --process-id 5120 --output baseline.gcdump dotnet-gcdump collect --process-id 5120 --output after_load.gcdump<\/code><\/li>\n\n\n\n
                      2. Open PerfView<\/strong> \u2192 Diff<\/strong><\/li>\n\n\n\n
                      3. Select both dumps \u2192 Analyze differences.<\/li>\n<\/ol>\n\n\n\n
                        PerfView will show:<\/p>\n\n\n\n
                          \n
                        • Object growth<\/li>\n\n\n\n
                        • Memory leaks<\/li>\n\n\n\n
                        • Which objects increased or decreased<\/li>\n<\/ul>\n\n\n\n
                          \n\n\n\n
                          \ud83d\ude80 Real Production-like Examples<\/strong><\/h1>\n\n\n\n
                          Example 7 \u2014 Detect Memory Leak in ASP.NET Core App<\/strong><\/h2>\n\n\n\n
                          You see memory keeps increasing in production.
                          Take a gcdump:<\/p>\n\n\n
                          dotnet-gcdump<\/span> collect<\/span> --process-id<\/span> 44312 --output<\/span> before_load<\/span>.gcdump<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Run a heavy load test for 10 minutes\u2026<\/p>\n\n\n\n
                          Take second dump:<\/p>\n\n\n
                          dotnet-gcdump<\/span> collect<\/span> --process-id<\/span> 44312 --output<\/span> after_load<\/span>.gcdump<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Analyze diff:<\/p>\n\n\n\n
                            \n
                          • List<SessionObject><\/code> grew by +120,000 objects<\/li>\n\n\n\n
                          • byte[]<\/code> objects in LOH increased<\/li>\n\n\n\n
                          • Some static dictionary retained references<\/li>\n<\/ul>\n\n\n\n
                            Result \u2192 Memory leak confirmed<\/strong>.<\/p>\n\n\n\n
                            \n\n\n\n
                            Example 8 \u2014 Identify Large Object Heap (LOH) Pressure<\/strong><\/h2>\n\n\n\n
                            App is slow. Using gcdump:<\/p>\n\n\n
                            dotnet-gcdump collect --process-id 5566\n<\/code><\/span><\/pre>\n\n\n
                            PerfView shows:<\/p>\n\n\n\n
                              \n
                            • LOH: 600 MB<\/strong><\/li>\n\n\n\n
                            • Large arrays: byte[] of sizes 1 MB each<\/li>\n\n\n\n
                            • Created during image resizing logic<\/li>\n<\/ul>\n\n\n\n
                              Solution:
                              Switch to shared buffers<\/strong>, or pooling<\/strong>.<\/p>\n\n\n\n
                              \n\n\n\n
                              Example 9 \u2014 High Allocation Rate Investigation<\/strong><\/h2>\n\n\n\n
                              dotnet-counters<\/code> shows Allocation Rate 800 MB\/sec<\/strong>.<\/p>\n\n\n\n
                              Take gc-dump:<\/p>\n\n\n
                              dotnet-gcdump<\/span> collect<\/span> --process-id<\/span> 6632 --output<\/span> high_alloc<\/span>.gcdump<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                              PerfView:<\/p>\n\n\n\n
                                \n
                              • Huge number of JObject<\/code> and JToken<\/code><\/li>\n\n\n\n
                              • Caused by unoptimized JSON-parsing inside loop<\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n
                                \ud83e\uddea Sample GCDump File Name Examples<\/strong><\/h1>\n\n\n\n
                                Dump filenames generated automatically:<\/p>\n\n\n
                                OrdersApi_20261125_091000<\/span>.gcdump<\/span>\nPaymentService_20261125_152200<\/span>.gcdump<\/span>\nBackgroundWorker_20261126_004500<\/span>.gcdump<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                                \n\n\n\n
                                \ud83d\udcc4 Sample dotnet-gcdump Output (Realistic)<\/strong><\/h1>\n\n\n\n
                                Example console output when capturing:<\/p>\n\n\n
                                PS> dotnet-gcdump collect --process-id 5566<\/span> --output api-memory-dump.gcdump\n\nStartTime<\/span>:       2026<\/span>-11<\/span>-25<\/span>T14:15<\/span>:03.123<\/span>Z\nProcess Name:    Orders.Api\nPID<\/span>:             5566<\/span>\nGC Mode:         Server GC\nCollecting...\nWriting gcdump to 'api-memory-dump.gcdump'<\/span>...\nComplete\nDump Size:       85.32<\/span> MB\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                \n\n\n\n
                                \ud83d\udd0d Example PerfView Analysis (What You See)<\/strong><\/h1>\n\n\n\n
                                Once opened in PerfView, you may see:<\/p>\n\n\n\n
                                \u2714 Heap Summary<\/h3>\n\n\n\n
                                  \n
                                • Total Heap: 1.2 GB<\/strong><\/li>\n\n\n\n
                                • Gen 0: 120 MB<\/li>\n\n\n\n
                                • Gen 1: 80 MB<\/li>\n\n\n\n
                                • Gen 2: 350 MB<\/li>\n\n\n\n
                                • LOH: 650 MB<\/li>\n<\/ul>\n\n\n\n
                                  \u2714 Top Object Types by Size<\/h3>\n\n\n\n
                                  Type<\/th>Count<\/th>Size<\/th><\/tr><\/thead>
                                  byte[]<\/td>2,450<\/td>420 MB<\/td><\/tr>
                                  JObject<\/td>50,000<\/td>200 MB<\/td><\/tr>
                                  Dictionary<string, object><\/td>8,000<\/td>130 MB<\/td><\/tr>
                                  String<\/td>450,000<\/td>80 MB<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                                  \u2714 Retention Graph<\/h3>\n\n\n\n
                                  You will see:<\/p>\n\n\n
                                  Static<\/span>: SomeCache<\/span>\n \u2514\u2500\u2500 Dictionary<\/span><string<\/span>, object<\/span>>\n       \u2514\u2500\u2500 DataObject<\/span>[]<\/span>\n             \u2514\u2500\u2500 byte<\/span>[]<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                                  This tells you what is keeping objects alive<\/strong> \u2192 leak root.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  \ud83c\udfaf Want me to generate a sample .gcdump<\/code> file for training?<\/strong><\/h1>\n\n\n\n
                                  I can generate:<\/p>\n\n\n\n
                                    \n
                                  • Fake GC dump<\/li>\n\n\n\n
                                  • PerfView screenshots<\/li>\n\n\n\n
                                  • Step-by-step lab manual<\/li>\n\n\n\n
                                  • PPT (PowerPoint) 10\u201315 slides<\/li>\n<\/ul>\n\n\n\n
                                    <\/p>\n","protected":false},"excerpt":{"rendered":"
                                    1. What is dotnet-gcdump? dotnet-gcdump is a lightweight .NET memory profiling tool that collects GC (Garbage Collector) heap dumps with minimal performance overhead. It gives you: It is part of… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-54191","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54191","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=54191"}],"version-history":[{"count":2,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54191\/revisions"}],"predecessor-version":[{"id":59887,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/54191\/revisions\/59887"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=54191"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=54191"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=54191"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}