Bobcares

Cloudflare logs to Splunk | How to link

Cloudflare logs to Splunk is an easy task with a little assistance from our experts. Read on to find out more. 

At Bobcares, we offer solutions for every query, big and small, as a part of our Server Management Services.

Let’s look at how our Support Team helped our customers learn more about enabling Cloudflare logs to Splunk.

How to link Cloudflare logs to Splunk

Cloudflare offers us in-detail logs of all our HTTP requests. We can use these logs to identify configuration adjustments, debug, improve security, create custom analytics, and so on. Furthermore, we can combine these request logs with other data sources like application server logs as well.

Cloudflare logs to splunk

Cloudflare’s Enterprise plan includes a feature called Logpush. It is responsible for delivering a batch of logs as a gzipped file. This file contains the data in the newline-delimited JSON format or as a JSON lines Open external link to our destination.

On the other hand, Splunk is a data platform that offers enterprise observability, limitless custom applications and unifies security as well. It is very helpful in searching through and monitoring big data. Additionally, it generates reports, alerts, and visualization to make our job easier.

Today, our Support team is going to demonstrate how to link Cloudflare logs to Splunk by enabling Logpush to Splunk. In fact, we can get this done via the Cloudflare dashboard or via API.

Enable Cloudflare Logpush to Splunk: Cloudflare Dashboard

  1. To begin with, log in to the Cloudflare dashboard and select the Enterprise domain we want to use with Logpush.
  2. Then, head to Logs under Analytics.
  3. Next, select Connect a service. This causes a modal window to open where there are a few additional steps to complete.
  4. After that, choose the dataset we want to push to the storage service.
  5. Then, choose the data field to include in our logs. We can remove or add fields at a later point in time by changing the settings in Logpush under Logs.
  6. Next, select Splunk.
  7. Then, enter the following information:
    • Splunk raw HTTP Event Collector URL
    • Channel ID
    • Auth Token
    • Source Type
    • Use insecure skip verify option
  8. Then click Validate access.
  9. Finally, select Save and Start Pushing in order to finish the process.

After following the above steps to link Cloudflare logs to Splunk, we will be able to see Splunk listed as a connected service in Logpush under Logs.

Enable Cloudflare Logpush to Splunk: API

  1. First, create a job with the corresponding endpoint URL as well as authentication parameters.
  2. Then, enable the job in order to start linking Cloudflare logs to Splunk.

[Need assistance with a different issue? We are available 24/7.]

Conclusion

In a nutshell, our skilled Support Engineers at Bobcares demonstrated how to start linking Cloudflare logs to Splunk.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF