{"id":11506,"date":"2019-03-14T09:45:51","date_gmt":"2019-03-14T09:45:51","guid":{"rendered":"http:\/\/www.appservgrid.com\/paw92\/?p=11506"},"modified":"2019-03-14T09:45:51","modified_gmt":"2019-03-14T09:45:51","slug":"collectl-an-advanced-all-in-one-performance-monitoring-tool-for-linux","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/03\/14\/collectl-an-advanced-all-in-one-performance-monitoring-tool-for-linux\/","title":{"rendered":"Collectl: An Advanced All-in-One Performance Monitoring Tool for Linux"},"content":{"rendered":"

The most important duty of a Linux system administrator is to make sure the system he\/she is administering is in a very good condition. There are many tools available for a Linux system admins that can help to monitor and display processes in a system such as\u00a0top<\/a>\u00a0and\u00a0htop<\/a>, but none of these tools can compete with\u00a0collectl<\/strong>.<\/p>\n

\n

\"Install<\/a><\/p>\n

Collectl: Linux Performance Monitoring<\/p>\n<\/div>\n

collectl<\/strong>\u00a0is a very nice feature rich command-line utility that can be used to collect performance data that describes the current system status. Unlike most of the other monitoring tools, collectl does not focus in a limited number of system metrics, instead it can gather information on many different types of system resources such as cpu, disk, memory, network, sockets, tcp, inodes, infiniband, lustre, memory, nfs, processes, quadrics, slabs and buddyinfo.<\/p>\n

A very good thing about using\u00a0collectl<\/strong>\u00a0is that it can also play the role of utilities that are designed with only a specific purpose such as top, ps,\u00a0iotop<\/a>\u00a0and many others. What are some features that make\u00a0colleclt<\/strong>\u00a0a useful tool?<\/p>\n

After doing a lot of research I have compiled a list with some of the most important features of the collectl command-line utility for you guys.<\/p>\n

Collectl Features<\/h4>\n
    \n
  1. It can run interactively, as a daemon or both.<\/li>\n
  2. It can display the output in many formats.<\/li>\n
  3. It has the ability to monitor almost any subsystem.<\/li>\n
  4. It can play the role of many other utilities such as ps, top, iotop, vmstat.<\/li>\n
  5. It has the ability to record and playback the captured data.<\/li>\n
  6. It can export the data in various file formats. (this is very useful when you want to analyse the data with external tools).<\/li>\n
  7. It can run as a service to monitor remote machines or an entire server cluster.<\/li>\n
  8. It can display the data in the terminal, write to a file or a socket.<\/li>\n<\/ol>\n

    How to Install collectl in Linux<\/h3>\n

    The\u00a0collectl<\/strong>\u00a0utility runs on all Linux distributions, the only thing it requires to run is perl, so make sure that you have\u00a0Perl<\/strong>\u00a0installed in your machine before installing collectl in your machine.<\/p>\n

    On Debian\/Ubuntu\/Linux Mint<\/h5>\n

    The following command can be used to install the collectl utility in Debian based machines such as Ubuntu.<\/p>\n

    $ sudo apt-get install collectl<\/pre>\n
    On RHEL\/CentOS\/Fedora<\/h5>\n
    If you are using Red Hat based distro, you can easily grab it from the repos with the yum command.<\/p>\n
    # yum install collectl<\/pre>\n
    Some Practical Examples Of The collectl Utility<\/h3>\n
    Once the installation of the collectl tool is finished, you can easily run it from the terminal, even without any option. The following command will display information on cpu, disk and network stats in a very short and human readable format.<\/p>\n
    # collectl<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#cpu sys inter  ctxsw KBRead  Reads KBWrit Writes   KBIn  PktIn  KBOut  PktOut \r\n  13   5   790   1322      0      0     92      7      4     13      0       5 \r\n  10   2   719   1186      0      0      0      0      3      9      0       4 \r\n  12   0   753   1188      0      0     52      3      2      5      0       6 \r\n  13   2   733   1063      0      0      0      0      1      1      0       1 \r\n  25   2   834   1375      0      0      0      0      1      1      0       1 \r\n  28   2   870   1424      0      0     36      7      1      1      0       1 \r\n  19   3   949   2271      0      0     44      3      1      1      0       1 \r\n  17   2   809   1384      0      0      0      0      1      6      0       6 \r\n  16   2   732   1348      0      0      0      0      1      1      0       1 \r\n  22   4   993   1615      0      0     56      3      1      2      0       3<\/pre>\n
    As you guys can see from the above output displayed in the terminal screen, it is very easy to work with the system metrics values present in the command output because it appears on a single line.<\/p>\n
    When the collectl utility is executed without any option it displays information about the following subsystems:<\/p>\n
      \n
    1. cpu<\/li>\n
    2. disks<\/li>\n
    3. network<\/li>\n<\/ol>\n
      Note<\/strong>: In our case, a subsystem is every type of a system resource that can be measured.<\/p>\n
      You can also display statistics for all subsystems except slabs by combining the command with the\u00a0\u2013all<\/strong>\u00a0option like shown below.<\/p>\n
      # collectl --all<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#cpu sys inter  ctxsw Cpu0 Cpu1 Free Buff Cach Inac Slab  Map   Fragments KBRead  Reads KBWrit Writes   KBIn  PktIn  KBOut  PktOut   IP  Tcp  Udp Icmp  Tcp  Udp  Raw Frag Handle Inodes  Reads Writes Meta Comm \r\n  16   3   817   1542  430  390   1G 175M   1G 683M 193M   1G nsslkjjebbk      0      0     24      3      1      1      0       1    0    0    0    0  623    0    0    0   8160 240829      0      0    0    0 \r\n  11   1   745   1324  316  426   1G 175M   1G 683M 193M   1G nsslkjjebbk      0      0      0      0      0      3      0       2    0    0    0    0  622    0    0    0   8160 240828      0      0    0    0 \r\n  15   2   793   1683  371  424   1G 175M   1G 683M 193M   1G ssslkjjebbk      0      0      0      0      1      1      0       1    0    0    0    0  622    0    0    0   8160 240829      0      0    0    0 \r\n  16   2   872   1875  427  446   1G 175M   1G 683M 193M   1G ssslkjjebbk      0      0     24      3      1      1      0       1    0    0    0    0  622    0    0    0   8160 240828      0      0    0    0 \r\n  24   2   842   1383  473  368   1G 175M   1G 683M 193M   1G ssslkjjebbk      0      0    168      6      1      1      0       1    0    0    0    0  622    0    0    0   8160 240828      0      0    0    0 \r\n  27   3   844   1099  478  365   1G 175M   1G 683M 193M   1G nsslkjjebbk      0      0      0      0      1      6      1       9    0    0    0    0  622    0    0    0   8160 240828      0      0    0    0 \r\n  26   5   823   1238  396  428   1G 175M   1G 683M 193M   1G ssslkjjebbk      0      0      0      0      2     11      3       9    0    0    0    0  622    0    0    0   8160 240828      0      0    0    0 \r\n  15   1   753   1276  361  391   1G 175M   1G 683M 193M   1G ssslkjjebbk      0      0     40      3      1      2      0       3    0    0    0    0  623    0    0    0   8160 240829      0      0    0    0<\/pre>\n
      But, how do you monitor the cpu usage with the help of the utility? The\u00a0\u2018-s<\/strong>\u2018 option should be used to controls which subsystem data is to be collected or played back.<\/p>\n
      For example the following command can be used to monitor the summary of the cpu usage.<\/p>\n
      # collectl -sc<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#cpu sys inter  ctxsw \r\n  15   2   749   1155 \r\n  16   3   772   1445 \r\n  14   2   793   1247 \r\n  27   4   887   1292 \r\n  24   1   796   1258 \r\n  16   1   743   1113 \r\n  15   1   743   1179 \r\n  14   1   706   1078 \r\n  15   1   764   1268<\/pre>\n
      What happens when you combine the command with \u201cscdn<\/strong>\u201c? The best way to learn how to use command-line tools is to practice as much as possible, so run the following command in your terminal and see what is going to happen.<\/p>\n
      # collectl -scdn<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#cpu sys inter  ctxsw KBRead  Reads KBWrit Writes   KBIn  PktIn  KBOut  PktOut \r\n  25   4   943   3333      0      0      0      0      1      1      0       2 \r\n  27   3   825   2910      0      0      0      0      1      1      0       1 \r\n  27   5   886   2531      0      0      0      0      0      0      0       1 \r\n  20   4   872   2406      0      0      0      0      1      1      0       1 \r\n  26   1   854   2091      0      0     20      2      1      1      0       1 \r\n  39   4  1004   3398      0      0      0      0      2      8      3       6 \r\n  41   6   955   2464      0      0     40      3      1      2      0       3 \r\n  25   7   890   1609      0      0      0      0      1      1      0       1 \r\n  16   2   814   1165      0      0    796     43      2      2      0       2 \r\n  14   1   779   1383      0      0     48      6      1      1      0       1 \r\n  11   2   795   1285      0      0      0      0      2     14      1      14<\/pre>\n
      You can easily understand that the default option is \u201ccdn<\/strong>\u201c, it stands for cpu, disks and network data. The result of the command is the same with the output of\u00a0\u201ccollectl -scn<\/strong>\u201d<\/p>\n
      If you want to collect data about the memory, use the following command.<\/p>\n
      # collectl -sm<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#Free Buff Cach Inac Slab  Map \r\n   1G 177M   1G 684M 193M   1G \r\n   1G 177M   1G 684M 193M   1G \r\n   1G 177M   1G 684M 193M   1G \r\n   1G 177M   1G 684M 193M   1G \r\n   1G 177M   1G 684M 193M   1G \r\n   1G 177M   1G 684M 193M   1G \r\n   1G 177M   1G 684M 193M   1G \r\n   1G 177M   1G 684M 193M   1G<\/pre>\n
      The above output is very useful when you want to get some detailed information on your memory usage, free memory and other important stuff for the performance of your system.<\/p>\n
      How about some data on tcp? Use the following command to do it.<\/p>\n
      # collectl -st<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#  IP  Tcp  Udp Icmp \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0 \r\n    0    0    0    0<\/pre>\n
      After you have gained some experience you can easily combine options to get the results you want. For example you can combine the \u201ct<\/strong>\u201d for tcp and \u201cc<\/strong>\u201d for cpu. The following command does that.<\/p>\n
      # collectl -stc<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#cpu sys inter  ctxsw   IP  Tcp  Udp Icmp \r\n  23   8   961   3136    0    0    0    0 \r\n  24   5   916   3662    0    0    0    0 \r\n  21   8   848   2408    0    0    0    0 \r\n  30  10   916   2674    0    0    0    0 \r\n  38   3   826   1752    0    0    0    0 \r\n  31   3   820   1408    0    0    0    0 \r\n  15   5   781   1335    0    0    0    0 \r\n  17   3   802   1314    0    0    0    0 \r\n  17   3   755   1218    0    0    0    0 \r\n  14   2   788   1321    0    0    0    0<\/pre>\n
      It is hard for us humans to remember all the available options so I am posting the summary list of subsystems supported by the tool.<\/p>\n
        \n
      1. b<\/strong>\u00a0\u2013 buddy info (memory fragmentation)<\/li>\n
      2. c<\/strong>\u00a0\u2013 CPU<\/li>\n
      3. d<\/strong>\u00a0\u2013 Disk<\/li>\n
      4. f<\/strong>\u00a0\u2013 NFS V3 Data<\/li>\n
      5. i<\/strong>\u00a0\u2013 Inode and File System<\/li>\n
      6. j<\/strong>\u00a0\u2013 Interrupts<\/li>\n
      7. l<\/strong>\u00a0\u2013 Lustre<\/li>\n
      8. m<\/strong>\u00a0\u2013 Memory<\/li>\n
      9. n<\/strong>\u00a0\u2013 Networks<\/li>\n
      10. s<\/strong>\u00a0\u2013 Sockets<\/li>\n
      11. t<\/strong>\u00a0\u2013 TCP<\/li>\n
      12. x<\/strong>\u00a0\u2013 Interconnect<\/li>\n
      13. y<\/strong>\u00a0\u2013 Slabs (system object caches)<\/li>\n<\/ol>\n
        A very important piece of data for a system administrator or a Linux user is the data collected on disk usage. The following command will help you to monitor the disk usage.<\/p>\n
        # collectl -sd<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n#\r\n#KBRead  Reads KBWrit Writes \r\n      0      0      0      0 \r\n      0      0      0      0 \r\n      0      0     92      7 \r\n      0      0      0      0 \r\n      0      0     36      3 \r\n      0      0      0      0 \r\n      0      0      0      0 \r\n      0      0    100      7 \r\n      0      0      0      0<\/pre>\n
        You can also use the \u201c-sD<\/strong>\u201d option to collect data on individual disks, but you have to know that information on total disks will not be reported.<\/p>\n
        # collectl -sD<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n\r\n# DISK STATISTICS (\/sec)\r\n#           Pct\r\n#Name       KBytes Merged  IOs Size  KBytes Merged  IOs Size  RWSize  QLen  Wait SvcTim Util\r\nsda              0      0    0    0      52     11    2   26      26     1     8      8    1\r\nsda              0      0    0    0       0      0    0    0       0     0     0      0    0\r\nsda              0      0    0    0      24      0    2   12      12     0     0      0    0\r\nsda              0      0    0    0     152      0    4   38      38     0     0      0    0\r\nsda              0      0    0    0     192     45    3   64      64     1    20     20    5\r\nsda              0      0    0    0     204      0    2  102     102     0     0      0    0\r\nsda              0      0    0    0       0      0    0    0       0     0     0      0    0\r\nsda              0      0    0    0     116     26    3   39      38     1    16     16    4\r\nsda              0      0    0    0       0      0    0    0       0     0     0      0    0\r\nsda              0      0    0    0       0      0    0    0       0     0     0      0    0\r\nsda              0      0    0    0      32      5    3   11      10     1    16     16    4\r\nsda              0      0    0    0       0      0    0    0       0     0     0      0    0<\/pre>\n
        You can also use other detail subsystems to collect detailed data. The following is a list of the detail subsystems.<\/p>\n
          \n
        1. C<\/strong>\u00a0\u2013 CPU<\/li>\n
        2. D<\/strong>\u00a0\u2013 Disk<\/li>\n
        3. E<\/strong>\u00a0\u2013 Environmental data (fan, power, temp), via ipmitool<\/li>\n
        4. F<\/strong>\u00a0\u2013 NFS Data<\/li>\n
        5. J<\/strong>\u00a0\u2013 Interrupts<\/li>\n
        6. L<\/strong>\u00a0\u2013 Lustre OST detail OR client Filesystem detail<\/li>\n
        7. N\u00a0\u2013 Networks<\/strong><\/li>\n
        8. T<\/strong>\u00a0\u2013 65 TCP counters only available in plot format<\/li>\n
        9. X<\/strong>\u00a0\u2013 Interconnect<\/li>\n
        10. Y<\/strong>\u00a0\u2013 Slabs (system object caches)<\/li>\n
        11. Z<\/strong>\u00a0\u2013 Processes<\/li>\n<\/ol>\n
          There are many available options in the collectl utility, but there is not enough time and space to cover them all in only one article. However it is worth mentioning and teaching how to use the utility as\u00a0top<\/strong>\u00a0and\u00a0ps<\/strong>.<\/p>\n
          It is very easy to make collectl work as the top utility, just run the following command in your terminal and you will see the similar output the\u00a0top<\/strong>\u00a0tool gives you when it is executed in your Linux system.<\/p>\n
          # collectl --top<\/strong>\r\n\r\n# TOP PROCESSES sorted by time (counters are \/sec) 13:11:02\r\n# PID  User     PR  PPID THRD S   VSZ   RSS CP  SysT  UsrT Pct  AccuTime  RKB  WKB MajF MinF Command\r\n^COuch!tecmint  20     1   40 R    1G  626M  0  0.01  0.14  15  28:48.24    0    0    0  109 \/usr\/lib\/firefox\/firefox \r\n 3403  tecmint  20     1   40 R    1G  626M  1  0.00  0.20  20  28:48.44    0    0    0  600 \/usr\/lib\/firefox\/firefox \r\n 5851  tecmint  20  4666    0 R   17M   13M  0  0.02  0.06   8  00:01.28    0    0    0    0 \/usr\/bin\/perl \r\n 1682  root     20  1666    2 R  211M   55M  1  0.02  0.01   3  03:10.24    0    0    0   95 \/usr\/bin\/X \r\n 3454  tecmint  20  3403    8 S  216M   45M  1  0.01  0.02   3  01:23.32    0    0    0    0 \/usr\/lib\/firefox\/plugin-container \r\n 4658  tecmint  20  4657    3 S  207M   17M  1  0.00  0.02   2  00:08.23    0    0    0  142 gnome-terminal \r\n 2890  tecmint  20  2571    3 S  340M   68M  0  0.00  0.01   1  01:19.95    0    0    0    0 compiz \r\n 3521  tecmint  20     1   24 S  710M  148M  1  0.01  0.00   1  01:47.84    0    0    0    0 skype \r\n    1  root     20     0    0 S    3M    2M  0  0.00  0.00   0  00:02.57    0    0    0    0 \/sbin\/init \r\n    2  root     20     0    0 S     0     0  1  0.00  0.00   0  00:00.00    0    0    0    0 kthreadd \r\n    3  root     20     2    0 S     0     0  0  0.00  0.00   0  00:00.60    0    0    0    0 ksoftirqd\/0 \r\n    5  root      0     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 kworker\/0:0H \r\n    7  root      0     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 kworker\/u:0H \r\n    8  root     RT     2    0 S     0     0  0  0.00  0.00   0  00:04.42    0    0    0    0 migration\/0 \r\n    9  root     20     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 rcu_bh \r\n   10  root     20     2    0 R     0     0  0  0.00  0.00   0  00:02.22    0    0    0    0 rcu_sched \r\n   11  root     RT     2    0 S     0     0  0  0.00  0.00   0  00:00.05    0    0    0    0 watchdog\/0 \r\n   12  root     RT     2    0 S     0     0  1  0.00  0.00   0  00:00.07    0    0    0    0 watchdog\/1 \r\n   13  root     20     2    0 S     0     0  1  0.00  0.00   0  00:00.73    0    0    0    0 ksoftirqd\/1 \r\n   14  root     RT     2    0 S     0     0  1  0.00  0.00   0  00:01.96    0    0    0    0 migration\/1 \r\n   16  root      0     2    0 S     0     0  1  0.00  0.00   0  00:00.00    0    0    0    0 kworker\/1:0H \r\n   17  root      0     2    0 S     0     0  1  0.00  0.00   0  00:00.00    0    0    0    0 cpuset<\/pre>\n
          And now last but not least, to use the collectl utility as the ps tool run the following command in your terminal. You will get information about processes in your system the same way as you do when you run the \u201cps<\/strong>\u201d command in your terminal.<\/p>\n
          # collectl -c1 -sZ -i:1<\/strong>\r\n\r\nwaiting for 1 second sample...\r\n\r\n### RECORD    1 >>> tecmint-vgn-z13gn <<< (1397979716.001) (Sun Apr 20 13:11:56 2014) ###\r\n\r\n# PROCESS SUMMARY (counters are \/sec)\r\n# PID  User     PR  PPID THRD S   VSZ   RSS CP  SysT  UsrT Pct  AccuTime  RKB  WKB MajF MinF Command\r\n    1  root     20     0    0 S    3M    2M  0  0.00  0.00   0  00:02.57    0    0    0    0 \/sbin\/init \r\n    2  root     20     0    0 S     0     0  1  0.00  0.00   0  00:00.00    0    0    0    0 kthreadd \r\n    3  root     20     2    0 S     0     0  0  0.00  0.00   0  00:00.60    0    0    0    0 ksoftirqd\/0 \r\n    5  root      0     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 kworker\/0:0H \r\n    7  root      0     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 kworker\/u:0H \r\n    8  root     RT     2    0 S     0     0  0  0.00  0.00   0  00:04.42    0    0    0    0 migration\/0 \r\n    9  root     20     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 rcu_bh \r\n   10  root     20     2    0 S     0     0  0  0.00  0.00   0  00:02.24    0    0    0    0 rcu_sched \r\n   11  root     RT     2    0 S     0     0  0  0.00  0.00   0  00:00.05    0    0    0    0 watchdog\/0 \r\n   12  root     RT     2    0 S     0     0  1  0.00  0.00   0  00:00.07    0    0    0    0 watchdog\/1 \r\n   13  root     20     2    0 S     0     0  1  0.00  0.00   0  00:00.73    0    0    0    0 ksoftirqd\/1 \r\n   14  root     RT     2    0 S     0     0  1  0.00  0.00   0  00:01.96    0    0    0    0 migration\/1 \r\n   16  root      0     2    0 S     0     0  1  0.00  0.00   0  00:00.00    0    0    0    0 kworker\/1:0H \r\n   17  root      0     2    0 S     0     0  1  0.00  0.00   0  00:00.00    0    0    0    0 cpuset \r\n   18  root      0     2    0 S     0     0  1  0.00  0.00   0  00:00.00    0    0    0    0 khelper \r\n   19  root     20     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 kdevtmpfs \r\n   20  root      0     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 netns \r\n   21  root     20     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 bdi-default \r\n   22  root      0     2    0 S     0     0  0  0.00  0.00   0  00:00.00    0    0    0    0 kintegrityd<\/pre>\n
          I am very sure that many Linux system administrators will like this tool and will feel its power when using it to the fullest. If you like to advance your knowledge about collectl to the next level refer to its manual pages and keep practicing.<\/p>\n
          Just type the following command in your terminal and start reading.<\/p>\n
          # man collectl<\/strong><\/pre>\n
          Reference Links<\/h3>\n
          collectl Homepage<\/a><\/p>\n
          Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
          The most important duty of a Linux system administrator is to make sure the system he\/she is administering is in a very good condition. There are many tools available for a Linux system admins that can help to monitor and display processes in a system such as\u00a0top\u00a0and\u00a0htop, but none of these tools can compete with\u00a0collectl. … <\/p>\n
          Continue reading “Collectl: An Advanced All-in-One Performance Monitoring Tool for Linux”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11506","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/11506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/comments?post=11506"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/11506\/revisions"}],"predecessor-version":[{"id":11507,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/11506\/revisions\/11507"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/media?parent=11506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/categories?post=11506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/tags?post=11506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}