Welcome!

@DevOpsSummit Authors: Destiny Bertucci, Pat Romanski, Yeshim Deniz, Dalibor Siroky, Liz McMillan

Related Topics: @DevOpsSummit, Java IoT, @CloudExpo

@DevOpsSummit: Article

New Logentries Cookbook for Chef By @Logentries | @DevOpsSummit [#DevOps]

First off, I assume you have a basic understanding of Chef and its technologies

New Logentries Cookbook for Chef
by Joe Heung

We have released our logentries_agent cookbook to supermarket.chef.io! You can check out the docs here, or I've developed the following brief tutorial to walk you through how to automate your installation of the Logentries Linux Agentin your own infrastructure.

First off, I assume you have a basic understanding of Chef and its technologies; if you're unfamiliar with Chef I recommend having a look at this overview. (Also, if you dont have a Logentries account, you can get create a free account here in just a couple of minutes.)

To get started, add the following to your Cheffile or Berksfile.

cookbook 'logentries_agent', '~> 0.2.0'

This will add logentries_agent to your cookbooks. By default the cookbook downloads the Logentries Linux Agent and registers the host machine to send its logs to logentries.com.

For this you will need to override 2 attributes, I recommend you override node[‘le'][‘account_key'] at an environment level or wrapper_cookbook level and node[‘le'][‘logs_to_follow'] at a cookbook level:

override['le']['account_key'] = '000000000000-0000-0000-0000-00000000' override['le']['logs_to_follow'] = [{:name => 'syslog', :log => '/var/log/syslog'},{:name => 'apache2', :log => '/var/log/apache2/*'}]

Once your server is provisioned with the these overrides, you should be able to see something like this on logentries.com

logentries_agent-cookbook-in-supermarket.chef.io

This is a very simple example of how you can automate sending to logentries.com with our Linux agent. However, here are multiple ways in which you can run the Logentries Agent. (I will briefly explain them below but if you would like a blog post outlining these in more detail please feel free to comment and I will provide you with more information!)

Default

no datahub and pull configuration from logentries.com

override['le']['account_key'] = override['le']['logs_to_follow'] = [{:name => 'syslog', :log => '/var/log/syslog'}]

This is the regular case as explained above where you send the data directly to Logentries and get the configuration for your logs from Logentries as well.

Local configuration only

override['le']['pull-server-side-config'] = false override['le']['logs_to_follow'] = [{:name => 'syslog', :log => '/var/log/syslog', :token => '00000000-0000-0000-0000-000000000000'}]

To send data to Logentries without specifying an account key, you can set override[‘le'][‘pull-server-side-config'] to false. This will only send the logs specified in the configuration file without contacting Logentries. In this case you have to create the logs in advance and know the tokens as well.

Datahub

override['le']['datahub']['enable'] = true override['le']['pull-server-side-config'] = false override['le']['datahub']['server_ip'] = '1.2.3.4' override['le']['datahub']['port'] = 10000 override['le']['logs_to_follow'] = [{:name => 'syslog', :log => '/var/log/syslog'}]

This scenario is for Datahub users looking to push a config and not need to register to send their logs to their Datahub instance.

Let us know if you have any questions, and we always love you hear your feedback!

More Stories By Trevor Parsons

Trevor Parsons is Chief Scientist and Co-founder of Logentries. Trevor has over 10 years experience in enterprise software and, in particular, has specialized in developing enterprise monitoring and performance tools for distributed systems. He is also a research fellow at the Performance Engineering Lab Research Group and was formerly a Scientist at the IBM Center for Advanced Studies. Trevor holds a PhD from University College Dublin, Ireland.

@DevOpsSummit Stories
ChatOps is an emerging topic that has led to the wide availability of integrations between group chat and various other tools/platforms. Currently, HipChat is an extremely powerful collaboration platform due to the various ChatOps integrations that are available. However, DevOps automation can involve orchestration and complex workflows. In his session at @DevOpsSummit at 20th Cloud Expo, Himanshu Chhetri, CTO at Addteq, will cover practical examples and use cases such as self-provisioning infrastructure/applications, self-remediation workflows, integrating monitoring and complimenting integrations between Atlassian tools and other top tools in the industry.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, which can process our conversational commands and orchestrate the outcomes we request across our personal and professional realm of connected devices.
The need for greater agility and scalability necessitated the digital transformation in the form of following equation: monolithic to microservices to serverless architecture (FaaS). To keep up with the cut-throat competition, the organisations need to update their technology stack to make software development their differentiating factor. Thus microservices architecture emerged as a potential method to provide development teams with greater flexibility and other advantages, such as the ability to deliver applications at warp speed using infrastructure as a service (IaaS) and platform as a service (PaaS) environments.
The use of containers by developers -- and now increasingly IT operators -- has grown from infatuation to deep and abiding love. But as with any long-term affair, the honeymoon soon leads to needing to live well together ... and maybe even getting some relationship help along the way. And so it goes with container orchestration and automation solutions, which are rapidly emerging as the means to maintain the bliss between rapid container adoption and broad container use among multiple cloud hosts. This BriefingsDirect cloud services maturity discussion focuses on new ways to gain container orchestration, to better use serverless computing models, and employ inclusive management to keep the container love alive.
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the public cloud best suits your organization, and what the future holds for operations and infrastructure engineers in a post-container world. Is a serverless world inevitable?