{"id":1014,"date":"2018-10-21T11:28:35","date_gmt":"2018-10-21T08:28:35","guid":{"rendered":"http:\/\/kifarunix.com\/?p=1014"},"modified":"2024-03-11T20:04:23","modified_gmt":"2024-03-11T17:04:23","slug":"how-to-configure-remote-logging-with-rsyslog-on-ubuntu-18-04","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/how-to-configure-remote-logging-with-rsyslog-on-ubuntu-18-04\/","title":{"rendered":"Configure Remote Logging with Rsyslog on Ubuntu 18.04"},"content":{"rendered":"\n<figure data-wp-context=\"{&quot;uploadedSrc&quot;:&quot;https:\\\/\\\/kifarunix.com\\\/wp-content\\\/uploads\\\/2018\\\/10\\\/remote-logging-with-rsyslog.png&quot;,&quot;figureClassNames&quot;:&quot;wp-block-image size-full&quot;,&quot;figureStyles&quot;:null,&quot;imgClassNames&quot;:&quot;wp-image-19846&quot;,&quot;imgStyles&quot;:null,&quot;targetWidth&quot;:1040,&quot;targetHeight&quot;:577,&quot;scaleAttr&quot;:false,&quot;ariaLabel&quot;:&quot;Enlarge image: Configure Remote Logging with Rsyslog on Ubuntu&quot;,&quot;alt&quot;:&quot;Configure Remote Logging with Rsyslog on Ubuntu&quot;}\" data-wp-interactive=\"core\/image\" class=\"wp-block-image size-full wp-lightbox-container\"><img loading=\"lazy\" decoding=\"async\" width=\"1040\" height=\"577\" data-wp-init=\"callbacks.setButtonStyles\" data-wp-on-async--click=\"actions.showLightbox\" data-wp-on-async--load=\"callbacks.setButtonStyles\" data-wp-on-async-window--resize=\"callbacks.setButtonStyles\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2018\/10\/remote-logging-with-rsyslog.png\" alt=\"Configure Remote Logging with Rsyslog on Ubuntu\" class=\"wp-image-19846\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2018\/10\/remote-logging-with-rsyslog.png 1040w, https:\/\/kifarunix.com\/wp-content\/uploads\/2018\/10\/remote-logging-with-rsyslog-768x426.png 768w\" sizes=\"(max-width: 1040px) 100vw, 1040px\" \/><button\n\t\t\tclass=\"lightbox-trigger\"\n\t\t\ttype=\"button\"\n\t\t\taria-haspopup=\"dialog\"\n\t\t\taria-label=\"Enlarge image: Configure Remote Logging with Rsyslog on Ubuntu\"\n\t\t\tdata-wp-init=\"callbacks.initTriggerButton\"\n\t\t\tdata-wp-on-async--click=\"actions.showLightbox\"\n\t\t\tdata-wp-style--right=\"context.imageButtonRight\"\n\t\t\tdata-wp-style--top=\"context.imageButtonTop\"\n\t\t>\n\t\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"12\" height=\"12\" fill=\"none\" viewBox=\"0 0 12 12\">\n\t\t\t\t<path fill=\"#fff\" d=\"M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z\" \/>\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n<p>In this tutorial, you will learn how to configure remote logging with <a href=\"https:\/\/www.rsyslog.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">Rsyslog<\/a> on Ubuntu 18.04. Configuring remote logging with Rsyslog on Ubuntu allows you to centralize and store log data on a remote server. Remote logging has several important benefits:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Makes it easier to monitor and analyze log data from multiple systems in one location.<\/li>\n\n\n\n<li>Simplifies the troubleshooting process, as you can review logs from various sources simultaneously.<\/li>\n\n\n\n<li>Storing logs on a separate server protects them from potential tampering or deletion on the local systems.<\/li>\n\n\n\n<li>In the event of a security incident, having centralized logs aids in forensic analysis, helping to identify the source and nature of the breach.<\/li>\n\n\n\n<li>Compliance to various standards by providing a unified and secure log storage solution.<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#configuring-remote-logging-with-rsyslog-on-ubuntu-18-04\">Configuring Remote Logging with Rsyslog on Ubuntu 18.04<\/a><ul><li><a href=\"#install-rsyslog-on-ubuntu-18-04\">Install Rsyslog on Ubuntu 18.04<\/a><\/li><li><a href=\"#allow-rsyslog-through-firewall\">Allow Rsyslog through Firewall<\/a><\/li><li><a href=\"#configure-ubuntu-18-04-as-a-log-server\">Configure Ubuntu 18.04 as a Log Server<\/a><\/li><li><a href=\"#define-allowed-senders\">Define Allowed Senders<\/a><\/li><li><a href=\"#configure-rsyslog-template\">Configure Rsyslog Template<\/a><\/li><li><a href=\"#configure-remote-client\">Configure Remote Client<\/a><ul><li><a href=\"#verify-remote-ports-connection\">Verify Remote Ports Connection<\/a><\/li><li><a href=\"#configure-client-rsyslog-to-sent-logs-to-remote-log-server\">Configure Client Rsyslog to Sent Logs to Remote Log Server<\/a><\/li><li><a href=\"#verify-log-reception-on-remote-log-server\">Verify Log Reception on Remote Log Server<\/a><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"configuring-remote-logging-with-rsyslog-on-ubuntu-18-04\">Configuring Remote Logging with Rsyslog on Ubuntu 18.04<\/h2>\n\n\n\n<p>Rsyslog can be configured in a client\/server model. When configured as a client, it sends logs to a remote server over the network via TCP\/UDP protocols. As a server, it receives logs over the network from remote client on port 514 TCP\/UDP.<\/p>\n\n\n\n<p>Rsyslog filters syslog messages based on selected filters. You may want to check out our previous article on <a href=\"https:\/\/kifarunix.com\/howtos\/a-basic-introduction-to-rsyslog-filters\/\" target=\"_blank\" rel=\"noopener noreferrer\">basic introduction to rsyslog filters<\/a>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"install-rsyslog-on-ubuntu-18-04\">Install Rsyslog on Ubuntu 18.04<\/h3>\n\n\n\n<p>Rsyslog is installed on Ubuntu 18.04 by default. You can verify this by checking the version of installed rsyslog.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">rsyslogd -v<\/pre>\n\n\n\n<p>If it is not installed, run the command below to install it.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code><span class=\"pre\">apt<\/span>&nbsp;<span class=\"pre\">install<\/span> <span class=\"pre\">rsyslog -y<\/span><\/code><\/pre>\n\n\n\n<p>Once the installation is done, start and enable the rsyslog service.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">systemctl enable --now rsyslog<\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"allow-rsyslog-through-firewall\">Allow Rsyslog through Firewall<\/h3>\n\n\n\n<p>If firewall is running, open rsyslog through it.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">ufw allow 514\/udp<\/pre>\n\n\n\n<p>Well, are you also interested in configuring syslog\/rsyslog on Solaris 11.4? Check the links below;<\/p>\n\n\n\n<p><a title=\"Configure Rsyslog on Solaris 11.4 to Send logs to Remote Log Server\" href=\"https:\/\/kifarunix.com\/configure-rsyslog-on-solaris-11-4-to-send-logs-to-remote-log-server\/\" target=\"_blank\" rel=\"bookmark noopener noreferrer\">Configure Rsyslog on Solaris 11.4 to Send logs to Remote Log Server<\/a><\/p>\n\n\n\n<p><a title=\"Configure Syslog on Solaris 11.4 for Remote Logging\" href=\"https:\/\/kifarunix.com\/how-to-configure-syslog-to-send-logs-to-remote-syslog-server-on-solaris-11-4\/\" target=\"_blank\" rel=\"bookmark noopener noreferrer\">Configure Syslog on Solaris 11.4 for Remote Logging<\/a><\/p>\n\n\n\n<p>Want to use NXLog to forward logs? Check out our article by following the link below;<\/p>\n\n\n\n<p><a title=\"Configure NXLog to Forward System Logs to Rsyslog Server on Ubuntu 18.04\" href=\"https:\/\/kifarunix.com\/configure-nxlog-to-forward-system-logs-to-rsyslog-server-on-ubuntu-18-04\/\" target=\"_blank\" rel=\"bookmark noopener noreferrer\">Configure NXLog to Forward System Logs to Rsyslog Server on Ubuntu 18.04<\/a><\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"configure-ubuntu-18-04-as-a-log-server\">Configure Ubuntu 18.04 as a Log Server<\/h3>\n\n\n\n<p>Now that rsyslog is installed and running, you need to configure it to run in server mode. To do so, edit the <strong>\/etc\/rsyslog.conf<\/strong> configuration file and uncomment the lines for UDP syslog reception in the <strong>MODULES<\/strong> section as shown below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">vim \/etc\/rsyslog.conf<\/pre>\n\n\n\n<pre class=\"scroll-box\"><code># provides UDP syslog reception\n<strong>module(load=\"imudp\")<\/strong>\n<strong>input(type=\"imudp\" port=\"514\")<\/strong>\n<\/code><\/pre>\n\n\n\n<p>Note that TCP syslog reception is way more reliable than UDP syslog and still pretty fast. The main reason is, that UDP might suffer of message loss. This happens when the syslog server must receive large bursts of messages. If the system buffer for UDP is full, all other messages will be dropped. With TCP, this will not happen. But sometimes it might be good to have a UDP server configured as well. That is, because some devices (like routers) are not able to send TCP syslog by design. In that case, you would need both syslog server types to have everything covered.<\/p>\n\n\n\n<p>By default UDP syslog is received on port 514. TCP syslog may need a different port because often the RPC service is using this port as well.<\/p>\n\n\n\n<p>To set rsyslog to run on a different TCP port, say TCP port, <strong>50514<\/strong>, uncomment the TCP reception lines and change the port as shown below;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code># provides TCP syslog reception\nmodule(load=\"imtcp\")\ninput(type=\"imtcp\" port=\"50514\")\n<\/code><\/pre>\n\n\n\n<p>Verify that rsyslog is now listening on two ports;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">netstat -4altunp | grep 514<\/pre>\n\n\n\n<pre class=\"scroll-box\"><code><strong>tcp<\/strong>        0      0 0.0.0.0:<strong>50514<\/strong>           0.0.0.0:*               LISTEN      10814\/rsyslogd      \n<strong>udp<\/strong>        0      0 0.0.0.0:<strong>514<\/strong>             0.0.0.0:*                           10814\/rsyslogd\n<\/code><\/pre>\n\n\n\n<p>You may notice that UDP port has no LISTEN state because it is connectionless and <span class=\"ILfuVd\">has no concept of &#8220;listening&#8221;, &#8220;established&#8221;, &#8220;closed&#8221;, or anything like that.<\/span><\/p>\n\n\n\n<p>Open the new port on UFW;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ufw allow 50514\/tcp<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"define-allowed-senders\">Define Allowed Senders<\/h3>\n\n\n\n<p>You may also want to explicitly set the remote clients that are allowed to to send syslog messages to rsyslogd. To achieve this, you can set a global directive using the <strong>$AllowedSender<\/strong> directive.<\/p>\n\n\n\n<p>Allowed sender lists can be defined for UDP and TCP senders separately. The syntax to specify them is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$AllowedSender &#91;UDP\/TCP], ip&#91;\/bits], ip&#91;\/bits]<\/code><\/pre>\n\n\n\n<p>Where:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>ip[\/bits]<\/strong> is a machine or network ip address as in &#8220;192.0.2.0\/24&#8221; or &#8220;192.0.2.10&#8221;. If the <strong>\/bits<\/strong> part is omitted, a single host is assumed. &#8220;\/0&#8221; is not allowed, because that would match any sending system.<\/li>\n<\/ul>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Hostnames<\/strong>, with and without wildcards, may also be provided. If so, the result of revers DNS resolution is used for filtering. Multiple allowed senders can be specified in a comma-delimited list.<\/li>\n<\/ul>\n\n\n\n<p>It is good to specify senders with high traffic volume before those with lower volume.<\/p>\n\n\n\n<p>As much as allowing specific hosts via this directive, a good idea to impose allowed sender limitations via firewalling.<\/p>\n\n\n\n<p>To allow specific hosts for either UDP or TCP logging, enter the following lines;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">vim \/etc\/rsyslog.conf<\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>...\n###########################\n#### GLOBAL DIRECTIVES ####\n###########################\n# $AllowedSender - specifies which remote systems are allowed to send syslog messages to rsyslogd\n<strong>$AllowedSender UDP, 192.168.43.0\/24, [::1]\/128, *.example.net, servera.example.com\n$AllowedSender TCP, 192.168.43.0\/24, [::1]\/128, *.example.net, servera.example.com<\/strong>\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"configure-rsyslog-template\">Configure Rsyslog Template<\/h3>\n\n\n\n<p>Templates are a key feature of rsyslog. Any output that is generated by rsyslog can be modified and formatted according to your needs with the use of templates. To create a template use the following syntax in <strong>\/etc\/rsyslog.conf<\/strong>:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">$template <em class=\"replaceable\">TEMPLATE_NAME<\/em>,\"<em class=\"replaceable\">text %PROPERTY% more text<\/em>\", [<span class=\"optional\"><em class=\"replaceable\">OPTION<\/em><\/span>]<\/pre>\n\n\n\n<p>Thus, we can create our template like;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code># provides TCP syslog reception\nmodule(load=\"imtcp\")\ninput(type=\"imtcp\" port=\"50514\")\n\n#Custom template to generate the log filename dynamically based on the client's IP address.\n<strong>$template RemInputLogs, \"\/var\/log\/remotelogs\/%FROMHOST-IP%\/%PROGRAMNAME%.log\"<\/strong>\n<strong>*.* ?RemInputLogs<\/strong>\n<\/code><\/pre>\n\n\n\n<p>Once you are done with configuration, you can now restart the <code>rsyslog<\/code> service by running the command below. Before you can restart rsyslogd, run a configuration check.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>rsyslogd -f \/etc\/rsyslog.conf -N1<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>rsyslogd: version 8.32.0, config validation run (level 1), master config \/etc\/rsyslog.conf\nrsyslogd: End of config validation run. Bye.<\/code><\/pre>\n\n\n\n<p>If all is well, proceed to restart rsyslog.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl restart rsyslog<\/code><\/pre>\n\n\n\n<p>Rsyslogd is now ready to receive logs from remote hosts.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"configure-remote-client\">Configure Remote Client<\/h3>\n\n\n\n<p>Now it is time to configure the remote client to send syslog messages to the remote syslog server. Login and proceed as follows.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"verify-remote-ports-connection\">Verify Remote Ports Connection<\/h4>\n\n\n\n<p>To verify connectivity to remote rsyslog server TCP port 50514, run the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><strong>telnet 192.168.43.154 50514<\/strong><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>Trying 192.168.43.154...\nConnected to 192.168.43.154.\nEscape character is '^]'.\n^]\n\ntelnet&gt;\n<\/code><\/pre>\n\n\n\n<p>Verify connectivity to UDP port 514. Since you cannot telnet to UDP port 514, use netcat command. On the server, run the command below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">nc -ul 514<\/pre>\n\n\n\n<p>On the client, run the command below, press ENTER and type anything. You should be able to see what you type on the server.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">nc -u 192.168.43.154 514<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"configure-client-rsyslog-to-sent-logs-to-remote-log-server\">Configure Client Rsyslog to Sent Logs to Remote Log Server<\/h4>\n\n\n\n<p>If all is good, edit the rsyslog configuration file as shown below;<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">vim \/etc\/rsyslog.conf<\/pre>\n\n\n\n<p>To send authentication logs over port 514\/UDP, add the following line at the end of the file.<\/p>\n\n\n\n<pre class=\"scroll-box\"><code># Send logs to remote syslog server over UDP\n<strong>auth,authpriv.* @192.168.43.154:514<\/strong>\n<\/code><\/pre>\n\n\n\n<p>To send all logs over port 50514\/TCP, add the following line at the end of the file.<\/p>\n\n\n\n<pre class=\"scroll-box\"><code># Send logs to remote syslog server over TCP 50514\n<strong>*.* @@192.168.43.154:50514<\/strong>\n<\/code><\/pre>\n\n\n\n<p>As a cushion just in case the remote rsyslog server goes down and your logs are so important you don&#8217;t want to loose, set the rsyslog disk queue for buffering in the rsyslog configuration file as shown below;<\/p>\n\n\n\n<pre class=\"scroll-box\"><code># Send logs to remote syslog server over UDP\n<strong>auth,authpriv.* @192.168.43.154:514\n<\/strong>\n# Define Disk Queue Buffer in case the server goes down\n<strong>$ActionQueueFileName queue<\/strong> # define a file name for disk assistance.\n<strong>$ActionQueueMaxDiskSpace 1g<\/strong>  # The maximum size that all queue files together will use on disk.\n<strong>$ActionQueueSaveOnShutdown on<\/strong>  # specifies that data should be saved at shutdown\n<strong>$ActionQueueType LinkedList<\/strong>  # holds enqueued messages in memory which makes the process very fast.&nbsp;\n<strong>$ActionResumeRetryCount -1<\/strong>  # prevents rsyslog from dropping messages when retrying to connect if server is not responding,\n<\/code><\/pre>\n\n\n\n<p>Restart the rsyslog service on the client.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">systemctl restart rsyslog<\/pre>\n\n\n\n<p>You can now log out of the client and login again. The authentication logs should be available on rsyslog server.<\/p>\n\n\n\n<p>Login to the server and verify the same.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">ls \/var\/log\/remotelogs\/<\/pre>\n\n\n\n<pre class=\"wp-block-preformatted\">127.0.0.1  192.168.43.214<\/pre>\n\n\n\n<h4 class=\"wp-block-heading\" id=\"verify-log-reception-on-remote-log-server\">Verify Log Reception on Remote Log Server<\/h4>\n\n\n\n<p>In our case, we send only authentication logs to remote rsyslog server.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">ls -1 \/var\/log\/remotelogs\/192.168.43.214\/<\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>sshd.log \nsudo.log\nsu.log\nsystemd-logind.log\n<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>tail -5 \/var\/log\/remotelogs\/192.168.43.214\/sshd.log<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>2024-01-13T11:01:33+03:00 mydevapp sshd[13430]: Disconnected from user amos 192.168.43.149 port 60808\n2024-01-13T11:01:33+03:00 mydevapp sshd[13363]: pam_unix(sshd:session): session closed for user amos\n2024-01-13T11:01:37+03:00 mydevapp sshd[13569]: pam_ecryptfs: Passphrase file wrapped\n2024-01-13T11:01:37+03:00 mydevapp sshd[13567]: Accepted password for amos from 192.168.43.149 port 60854 ssh2\n2024-01-13T11:01:37+03:00 mydevapp sshd[13567]: pam_unix(sshd:session): session opened for user amos by (uid=0)\n<\/code><\/pre>\n\n\n\n<p>That is all on Rsyslog remote logging.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this tutorial, you will learn how to configure remote logging with Rsyslog on Ubuntu 18.04. Configuring remote logging with Rsyslog on Ubuntu allows you<\/p>\n","protected":false},"author":1,"featured_media":19846,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[121,191],"tags":[193,186,192],"class_list":["post-1014","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-howtos","category-rsyslog","tag-remote-logging","tag-rsyslog","tag-syslog","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/1014"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=1014"}],"version-history":[{"count":18,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/1014\/revisions"}],"predecessor-version":[{"id":21034,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/1014\/revisions\/21034"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media\/19846"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=1014"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=1014"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=1014"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}