{"id":7668,"date":"2024-06-04T21:39:38","date_gmt":"2024-06-05T04:39:38","guid":{"rendered":"https:\/\/ioflood.com\/blog\/?p=7668"},"modified":"2024-06-05T13:49:12","modified_gmt":"2024-06-05T20:49:12","slug":"install-grafana-loki-linux","status":"publish","type":"post","link":"https:\/\/ioflood.com\/blog\/install-grafana-loki-linux\/","title":{"rendered":"How to Install Grafana Loki on Your Linux System"},"content":{"rendered":"
\n
\"Image<\/figure>\n<\/div>\n

Log aggregation and monitoring capabilities is crucial for managing our customer’s dedicated cloud server<\/a> systems at IOFLOOD<\/a>. While evaluating possible solutions we found that Grafana Loki, with its lightweight and scalable log aggregation system, can provide valuable insights into system logs and metrics. This article provides details on installing Grafana Loki on Linux, to assist our customers and fellow developers in gaining visibility into log data.<\/p>\n

In this tutorial, we will guide you on how to install the Grafana Loki command on your Linux system.<\/strong> We will delve into compiling Grafana Loki from source, installing a specific version, and finally, how to use the Grafana Loki command and ensure it’s installed correctly.<\/p>\n

So, let’s dive in and begin installing Grafana Loki on your Linux system!<\/p>\n

TL;DR: How Do I Install Grafana Loki on Linux?<\/h2>\n

\n To install Grafana Loki on Debian-based systems like Ubuntu, use sudo apt-get install loki<\/code>. For RPM-based systems like CentOS, use sudo yum install loki<\/code>. You can also install Grafana Loki by first downloading the binary from the Loki GitHub repository<\/a>, then configuring Loki, and finally starting the Loki server.\n<\/p><\/blockquote>\n

Here’s a basic example of how you might do this:<\/p>\n

# Download Loki binary\nwget https:\/\/github.com\/grafana\/loki\/releases\/download\/v2.4.1\/loki-linux-amd64.zip\n\n# Unzip the downloaded file\nunzip loki-linux-amd64.zip\n\n# Configure Loki (this is a basic configuration, your needs may vary)\ncat << EOF > loki-local-config.yaml\nauth_enabled: false\n\nserver:\n  http_listen_port: 3100\n\ningester:\n  lifecycler:\n    address: 127.0.0.1\n    ring:\n      kvstore:\n        store: inmemory\n      replication_factor: 1\n    final_sleep: 0s\n  chunk_idle_period: 1h       # Any chunk not receiving new logs in this time will be flushed\n  max_chunk_age: 1h           # All chunks will be flushed when they hit this age, default is 1h\n  chunk_target_size: 1048576  # Loki will attempt to build chunks up to 1.5MB, flushing first if chunk_idle_period or max_chunk_age is reached first\n  chunk_retain_period: 30s    # Must be greater than index read cache TTL if using an index cache (Default index read cache TTL is 5m)\n  max_transfer_retries: 0     # Chunk transfers disabled\n\nschema_config:\n  configs:\n    - from: 2020-10-24\n      store: boltdb-shipper\n      object_store: filesystem\n      schema: v11\n      index:\n        prefix: index_\n        period: 24h\n\nstorage_config:\n  boltdb_shipper:\n    active_index_directory: \/loki\/boltdb-shipper-active\n    cache_location: \/loki\/boltdb-shipper-cache\n    cache_ttl: 24h         # Can be increased for faster performance over longer query periods, uses more disk space\n    shared_store: filesystem\n  filesystem:\n    directory: \/loki\/chunks\n\ncompactor:\n  working_directory: \/loki\/boltdb-shipper-compactor\n  shared_store: filesystem\n\nlimits_config:\n  reject_old_samples: true\n  reject_old_samples_max_age: 168h\n\nchunk_store_config:\n  max_look_back_period: 0s\n\ntable_manager:\n  retention_deletes_enabled: false\n  retention_period: 0s\nEOF\n\n# Start Loki server\n.\/loki-linux-amd64 -config.file=loki-local-config.yaml\n\n# Output:\n# level=info ts=2022-03-01T12:00:00.123456789Z caller=main.go:130 msg=\"Starting Loki\" version=\"(version=2.4.1, branch=HEAD, revision=abcdef1)\"\n# level=info ...\n<\/code><\/pre>\n
This is a basic way to install Grafana Loki on Linux, but there’s much more to learn about installing and using Grafana Loki. Continue reading for more detailed information, advanced installation options, and troubleshooting tips.<\/p>\n
Getting Started with Grafana Loki<\/h2>\n
Grafana Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be cost-effective and easy to operate, as it does not index the content of the logs but rather a set of labels for each log stream. Loki is like Prometheus, but for logs, making both logs and metrics available in a single, unified platform.<\/p>\n
Installing Grafana Loki with APT<\/h3>\n
For distributions like Ubuntu and Debian, you can use the APT package manager to install Grafana Loki. Here’s a step-by-step guide on how to do it:<\/p>\n
# Update your APT package lists\nsudo apt update\n\n# Install unzip if it's not installed already\nsudo apt install unzip\n\n# Download Loki binary\nwget https:\/\/github.com\/grafana\/loki\/releases\/download\/v2.4.1\/loki-linux-amd64.zip\n\n# Unzip the downloaded file\nunzip loki-linux-amd64.zip\n\n# Output:\n# Archive:  loki-linux-amd64.zip\n#   inflating: loki-linux-amd64\n<\/code><\/pre>\n
In the code block above, we first updated our APT package lists with sudo apt update<\/code>. Then, we installed unzip<\/code> to extract the Loki binary. We downloaded the Loki binary with wget<\/code> and finally unzipped the file.<\/p>\n
Installing Grafana Loki with YUM<\/h3>\n
For distributions like CentOS and AlmaLinux, the YUM package manager is used. Here’s how you can install Grafana Loki using YUM:<\/p>\n
# Update your YUM package lists\nsudo yum check-update\n\n# Install unzip if it's not installed already\nsudo yum install unzip\n\n# Download Loki binary\nwget https:\/\/github.com\/grafana\/loki\/releases\/download\/v2.4.1\/loki-linux-amd64.zip\n\n# Unzip the downloaded file\nunzip loki-linux-amd64.zip\n\n# Output:\n# Archive:  loki-linux-amd64.zip\n#   inflating: loki-linux-amd64\n<\/code><\/pre>\n
In the code block above, we first updated our YUM package lists with sudo yum check-update<\/code>. Then, we installed unzip<\/code> to extract the Loki binary. We downloaded the Loki binary with wget<\/code> and finally unzipped the file.<\/p>\n
In both methods, we now have Loki binary ready to be configured and used in our Linux system.<\/p>\n
Installing Grafana Loki from Source<\/h2>\n
Compiling from source allows you to get the latest features and improvements in Grafana Loki that may not have been released in the official packages yet. Here’s how you can compile and install Grafana Loki from source:<\/p>\n
# Install Go if it's not installed already\nsudo apt install golang\n\n# Clone the Loki repository\ngit clone https:\/\/github.com\/grafana\/loki.git\n\n# Go to the Loki directory\n cd loki\n\n# Build Loki\nmake loki\n\n# Output:\n# ...\n# GO111MODULE=on go build -mod=vendor -o cmd\/loki\/loki -ldflags \"-s -w -X github.com\/grafana\/loki\/pkg\/build.Branch= -X github.com\/grafana\/loki\/pkg\/build.Version= -X github.com\/grafana\/loki\/pkg\/build.Revision= -X github.com\/grafana\/loki\/pkg\/build.BuildUser= -X github.com\/grafana\/loki\/pkg\/build.BuildDate= \" .\/cmd\/loki\n# ...\n<\/code><\/pre>\n
In the code block above, we first installed Go, a requirement for building Loki from source. We then cloned the Loki repository and navigated into the Loki directory. Finally, we built Loki using the make loki<\/code> command.<\/p>\n
Specific Versions of Grafana Loki<\/h2>\n
Installing Specific Versions from Source<\/h3>\n
If you want to install a specific version of Grafana Loki from source, you can do so by checking out the specific Git tag before building. Here’s how:<\/p>\n
# Clone the Loki repository\n git clone https:\/\/github.com\/grafana\/loki.git\n\n# Go to the Loki directory\n cd loki\n\n# Check out the specific version\n git checkout v2.4.1\n\n# Build Loki\n make loki\n\n# Output:\n# ...\n# GO111MODULE=on go build -mod=vendor -o cmd\/loki\/loki -ldflags \"-s -w -X github.com\/grafana\/loki\/pkg\/build.Branch= -X github.com\/grafana\/loki\/pkg\/build.Version= -X github.com\/grafana\/loki\/pkg\/build.Revision= -X github.com\/grafana\/loki\/pkg\/build.BuildUser= -X github.com\/grafana\/loki\/pkg\/build.BuildDate= \" .\/cmd\/loki\n# ...\n<\/code><\/pre>\n
In the code block above, we first cloned the Loki repository and navigated into the Loki directory. We then checked out the specific version of Loki we wanted to install using git checkout<\/code>. Finally, we built Loki using the make loki<\/code> command.<\/p>\n
Installing Specific Versions with APT and YUM<\/h3>\n
If you want to install a specific version of Grafana Loki using APT or YUM, you can do so by specifying the version in the install command. However, this only works if the version you want is available in the package repository. Here’s how you can do it:<\/p>\n
APT<\/h4>\n
# Install a specific version of Loki with APT\nsudo apt install loki=2.4.1\n<\/code><\/pre>\n
YUM<\/h4>\n
# Install a specific version of Loki with YUM\nsudo yum install loki-2.4.1\n<\/code><\/pre>\n
Version Comparison<\/h3>\n
Different versions of Grafana Loki come with different features and improvements. Here’s a comparison of the recent versions:<\/p>\n\n\n\n\n\n\n\n
Version<\/th>\nKey Features<\/th>\n<\/tr>\n<\/thead>\n
2.4.1<\/td>\nImproved query performance, bug fixes<\/td>\n<\/tr>\n
2.3.0<\/td>\nNew Loki operator, improved query performance<\/td>\n<\/tr>\n
2.2.1<\/td>\nBug fixes, improved stability<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Verifying Installation and Basic Usage<\/h2>\n
Verifying Installation<\/h3>\n
You can verify that Grafana Loki is installed correctly by running the following command:<\/p>\n
# Check Loki version\n.\/loki-linux-amd64 --version\n\n# Output:\n# loki, version 2.4.1 (branch: HEAD, revision: abcdef1)\n# build user:       root@abcdef1234\n# build date:       20220301-12:00:00\n# go version:       go1.16.3\n# platform:         linux\/amd64\n<\/code><\/pre>\n
In the code block above, we ran the --version<\/code> command on the Loki binary. The output shows the version of Loki installed, the build user, build date, Go version, and platform.<\/p>\n
Basic Usage<\/h3>\n
You can use Grafana Loki to aggregate logs by running it with a configuration file. Here’s a basic example:<\/p>\n
# Start Loki server\n.\/loki-linux-amd64 -config.file=loki-local-config.yaml\n\n# Output:\n# level=info ts=2022-03-01T12:00:00.123456789Z caller=main.go:130 msg=\"Starting Loki\" version=\"(version=2.4.1, branch=HEAD, revision=abcdef1)\"\n# level=info ...\n<\/code><\/pre>\n
In the code block above, we started the Loki server with a configuration file loki-local-config.yaml<\/code>. The output shows that Loki has started successfully.<\/p>\n
Alternative Log Aggregation Tools<\/h2>\n
While Grafana Loki offers a powerful and efficient solution for log aggregation in Linux, it’s not the only tool available. Other popular log aggregation tools include Fluentd and Logstash, each with their unique features, advantages, and disadvantages.<\/p>\n
Fluentd: An Open Source Data Collector<\/h3>\n
Fluentd is an open source data collector, which lets you unify the data collection and consumption for better use and understanding of data.<\/p>\n
To install Fluentd, you can use the following commands:<\/p>\n
# Install Fluentd\ncurl -L https:\/\/toolbelt.treasuredata.com\/sh\/install-ubuntu-bionic-td-agent3.sh | sh\n\n# Output:\n# ...\n# td-agent 3.3.0 Copyright 2004-2018 Treasure Data\n# Installed\n<\/code><\/pre>\n
In the code block above, we installed Fluentd using a script provided by Treasure Data, the company behind Fluentd. The output shows that Fluentd has been installed successfully.<\/p>\n
Logstash: Server-side Data Processing Pipeline<\/h3>\n
Logstash is a server-side data processing pipeline that ingests data from multiple sources simultaneously, transforms it, and then sends it to your favorite ‘stash.’<\/p>\n
To install Logstash, you can use the following commands:<\/p>\n
# Download and install the Public Signing Key\nwget -qO - https:\/\/artifacts.elastic.co\/GPG-KEY-elasticsearch | sudo apt-key add -\n\n# Save the repository definition to \/etc\/apt\/sources.list.d\/elastic-7.x.list\n echo \"deb https:\/\/artifacts.elastic.co\/packages\/7.x\/apt stable main\" | sudo tee -a \/etc\/apt\/sources.list.d\/elastic-7.x.list\n\n# Update your system\nsudo apt-get update\n\n# Install Logstash\nsudo apt-get install logstash\n\n# Output:\n# Reading package lists... Done\n# Building dependency tree\n# Reading state information... Done\n# logstash is already the newest version (1:7.16.2-1).\n# 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.\n<\/code><\/pre>\n
In the code block above, we first downloaded and installed the public signing key for Elastic, the company behind Logstash. We then added the Elastic repository to our APT sources list. After updating our system, we installed Logstash. The output shows that Logstash has been installed successfully.<\/p>\n
Comparing Loki, Fluentd, and Logstash<\/h3>\n\n\n\n\n\n\n\n
<\/th>\nLoki<\/th>\nFluentd<\/th>\nLogstash<\/th>\n<\/tr>\n<\/thead>\n
Ease of Use<\/td>\nHigh<\/td>\nMedium<\/td>\nMedium<\/td>\n<\/tr>\n
Performance<\/td>\nHigh<\/td>\nHigh<\/td>\nMedium<\/td>\n<\/tr>\n
Flexibility<\/td>\nHigh<\/td>\nHigh<\/td>\nHigh<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
While Loki, Fluentd, and Logstash all offer powerful features for log aggregation, they each have their strengths and weaknesses. Loki stands out for its ease of use and high performance, making it an excellent choice for beginners and large-scale deployments. Fluentd and Logstash offer high flexibility and can handle a wide variety of data sources, but they may require more configuration and resources.<\/p>\n
Ultimately, the best tool for you depends on your specific needs and resources. We recommend trying out each tool and seeing which one fits your workflow best.<\/p>\n
Troubleshooting Loki Installations<\/h2>\n
While installing Grafana Loki on Linux is generally straightforward, you may encounter some issues. Here are some common problems and their solutions.<\/p>\n
Issue: Failed to Download Loki Binary<\/h3>\n
If you encounter an error while downloading the Loki binary, it may be due to network issues or the specified version not being available. To troubleshoot this issue, check your network connection and verify the version of Loki you are trying to download.<\/p>\n
# Check network connection\nping -c 3 www.google.com\n\n# Output:\n# PING www.google.com (172.217.22.36) 56(84) bytes of data.\n# 64 bytes from lhr48s22-in-f4.1e100.net (172.217.22.36): icmp_seq=1 ttl=119 time=10.6 ms\n# ...\n<\/code><\/pre>\n
In the code block above, we used the ping<\/code> command to check the network connection. If the command returns a response, it means your network connection is working correctly.<\/p>\n
Issue: Loki Server Not Starting<\/h3>\n
If the Loki server is not starting, it may be due to a configuration issue. Check your Loki configuration file for any errors.<\/p>\n
# Check Loki configuration file\ncat loki-local-config.yaml\n\n# Output:\n# auth_enabled: false\n# ...\n<\/code><\/pre>\n
In the code block above, we used the cat<\/code> command to display the content of the Loki configuration file. Check the output for any errors or missing values.<\/p>\n
Issue: Loki Command Not Found<\/h3>\n
If you encounter a ‘command not found’ error when trying to run Loki, it may be because the Loki binary is not in your PATH. To resolve this issue, you can specify the full path to the Loki binary when running it, or add it to your PATH.<\/p>\n
# Add Loki binary to PATH\nexport PATH=$PATH:\/path\/to\/loki-binary\n\n# Check if Loki is in PATH\nwhich loki-linux-amd64\n\n# Output:\n# \/path\/to\/loki-binary\/loki-linux-amd64\n<\/code><\/pre>\n
In the code block above, we added the Loki binary to the PATH using the export<\/code> command. We then checked if Loki is in the PATH using the which<\/code> command. The output shows the full path to the Loki binary.<\/p>\n
Remember, the best way to avoid troubleshooting is to follow the installation instructions carefully and understand each step. If you still encounter issues, don’t hesitate to seek help from the community or professional support.<\/p>\n
What is Log Aggregation?<\/h2>\n
Log aggregation is a critical aspect of system administration and security. It involves collecting and centralizing log data from different sources into one place. This process makes it easier to monitor systems, troubleshoot issues, and analyze data. Let’s take a closer look at what log aggregation is and why it’s important.<\/p>\n
The Importance of Log Aggregation<\/h3>\n
In a typical IT infrastructure, logs are generated by various systems, applications, and devices. These logs contain valuable information about the operations and performance of these sources. However, when these logs are scattered across different locations, it can be difficult to make sense of the data.<\/p>\n
# Viewing logs of a Linux system\njournalctl -xe\n\n# Output:\n# -- Logs begin at Mon 2022-02-28 14:51:16 UTC, end at Tue 2022-03-01 15:00:02 UTC. --\n# Mar 01 15:00:01 ubuntu systemd[1]: Started Daily apt download activities.\n# Mar 01 15:00:02 ubuntu systemd[1]: apt-daily.timer: Succeeded.\n# ...\n<\/code><\/pre>\n
In the code block above, we used the journalctl -xe<\/code> command to view the logs of a Linux system. The output shows various logs, including system startups and application activities.<\/p>\n
Log aggregation centralizes these logs, making it easier to monitor systems, troubleshoot issues, and analyze data. It’s a crucial component of effective system administration and security.<\/p>\n
Grafana Loki: A Powerful Log Aggregation Tool<\/h3>\n
Grafana Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It’s designed to be very cost-effective and easy to operate, as it does not index the content of the logs, but rather a set of labels for each log stream.<\/p>\n
Grafana Loki is like Prometheus, but for logs, making both logs and metrics available in a single, unified platform. It integrates deeply into Grafana, providing a seamless experience for querying and visualizing logs.<\/p>\n
# Querying logs with Loki\nloki-cli query \"{job='varlogs'}\"\n\n# Output:\n# {job=\"varlogs\", filename=\"\/var\/log\/syslog\"} Feb 28 14:51:16 ubuntu systemd[1]: Mounted Huge Pages File System.\n# {job=\"varlogs\", filename=\"\/var\/log\/syslog\"} Feb 28 14:51:16 ubuntu systemd[1]: Mounted POSIX Message Queue File System.\n# ...\n<\/code><\/pre>\n
In the code block above, we used the loki-cli query<\/code> command to query logs with Loki. The output shows logs from the varlogs<\/code> job, including system startups and application activities.<\/p>\n
By understanding the importance of log aggregation and the capabilities of Grafana Loki, you can better manage and secure your IT infrastructure.<\/p>\n
Practical Uses of Log Aggregation<\/h2>\n
In system administration and security, log aggregation plays a pivotal role. It provides a consolidated view of what’s happening across various applications and infrastructure components. Without log aggregation, sifting through individual log files can be tedious and time-consuming, making it hard to spot trends or anomalies.<\/p>\n
# A simple log aggregation command using grep\ngrep 'ERROR' \/var\/log\/*.log\n\n# Output:\n# \/var\/log\/syslog:Jan  1 00:00:01 myhost ERROR An error event\n# \/var\/log\/auth.log:Jan  1 00:00:02 myhost ERROR Another error event\n<\/code><\/pre>\n
In the code block above, we’re using grep<\/code> to aggregate error messages from all log files in the \/var\/log<\/code> directory. This simple example demonstrates how log aggregation can help system administrators and security professionals quickly identify and respond to issues.<\/p>\n
Exploring Related Concepts<\/h2>\n
Log aggregation is just the beginning. Once logs are aggregated, they can be analyzed for valuable insights. Log analysis involves examining log entries to understand how systems and applications are performing and to identify any potential issues. Monitoring, on the other hand, is the real-time observation of systems and applications to ensure they’re functioning as expected.<\/p>\n
# A simple log analysis command using awk\nawk '\/ERROR\/ {count++} END {print count}' \/var\/log\/syslog\n\n# Output:\n# 42\n<\/code><\/pre>\n
In the code block above, we’re using awk<\/code> to count the number of error messages in the system log file. This is a simple example of log analysis that can help us understand the frequency of errors in our system.<\/p>\n
Further Resources for Mastering Log Aggregation and Analysis<\/h3>\n
To delve deeper into the world of log aggregation, analysis, and monitoring, here are some resources that you might find helpful:<\/p>\n
    \n
  1. Grafana Loki Documentation<\/a>: Comprehensive guide on how to use Grafana Loki, including installation, configuration, and querying logs.<\/p>\n<\/li>\n
  2. \n
    The ELK Stack: Elasticsearch, Logstash, and Kibana<\/a>: Learn about the ELK Stack, another popular log aggregation and analysis solution.<\/p>\n<\/li>\n
  3. \n
    Fluentd Documentation<\/a>: In-depth resource on how to use Fluentd for unified logging layer.<\/p>\n<\/li>\n<\/ol>\n
    These resources provide a wealth of information that can help you master log aggregation, analysis, and monitoring, and improve your system administration and security skills.<\/p>\n
    Recap: Installing Grafana Loki<\/h2>\n
    In this exhaustive guide, we’ve navigated through the process of installing Grafana Loki, an efficient log aggregation system, on Linux. We’ve covered the importance of log aggregation, the role of Grafana Loki in the landscape of log management, and the steps to install and configure it on your Linux system.<\/p>\n
    We began with the basics, outlining how to install Grafana Loki on APT-based distributions like Debian and Ubuntu, and YUM-based distributions like CentOS and AlmaLinux. We then ventured into intermediate territory, discussing advanced installation methods such as installing from source and installing specific versions.<\/p>\n
    We also tackled common issues you might encounter during the installation and usage of Grafana Loki, providing you with practical solutions and workarounds. Additionally, we explored alternative approaches to log aggregation, comparing Grafana Loki with Fluentd and Logstash.<\/p>\n
    Here’s a quick comparison of these log aggregation tools:<\/p>\n\n\n\n\n\n\n\n
    Tool<\/th>\nEase of Use<\/th>\nPerformance<\/th>\nFlexibility<\/th>\n<\/tr>\n<\/thead>\n
    Grafana Loki<\/td>\nHigh<\/td>\nHigh<\/td>\nHigh<\/td>\n<\/tr>\n
    Fluentd<\/td>\nMedium<\/td>\nHigh<\/td>\nHigh<\/td>\n<\/tr>\n
    Logstash<\/td>\nMedium<\/td>\nMedium<\/td>\nHigh<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    Whether you’re just starting out with Grafana Loki or looking to deepen your understanding of log aggregation tools, we hope this guide has been a valuable resource. With this knowledge, you’re well-equipped to manage logs efficiently and make informed decisions on the best tools for your specific needs.<\/p>\n
    Log aggregation is a critical aspect of system administration and security, and Grafana Loki offers a powerful solution for this task. Happy log aggregating!<\/p>\n","protected":false},"excerpt":{"rendered":"
    Log aggregation and monitoring capabilities is crucial for managing our customer’s dedicated cloud server systems at IOFLOOD. While evaluating possible solutions we found that Grafana Loki, with its lightweight and scalable log aggregation system, can provide valuable insights into system logs and metrics. This article provides details on installing Grafana Loki on Linux, to assist […]<\/p>\n","protected":false},"author":1,"featured_media":21072,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-7668","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","cat-3-id","has_thumb"],"_links":{"self":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts\/7668","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/comments?post=7668"}],"version-history":[{"count":12,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts\/7668\/revisions"}],"predecessor-version":[{"id":21110,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts\/7668\/revisions\/21110"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/media\/21072"}],"wp:attachment":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/media?parent=7668"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/categories?post=7668"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/tags?post=7668"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}