Feed
Pro
Search

Author

Write
Drafts

Bug0 - The AI-native e2e QA regression testing Passmark - The open-source AI framework for regression testing Hackathons Changelog Brand Hashnode gql skill - let your AI agent publish to your Hashnode blog The Foreword by Hashnode - official blog from the Hashnode team @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap
Sign in

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Parsing Network Devices Logs with the Elastic Stack" | Hashnode

FeedDiscussion

David Flores (aka: netpanda)

Network Automation Geek!

Mar 16, 2020

Parsing Network Devices Logs with the Elastic Stack

Intro This post is part of several posts related to Network Infrastructure Monitoring using the Elastic Stack. As a starting point lets start with the basics for monitoring events on you network infrastructure -> Logs. There are multiple blogs, artic...

davidban77.hashnode.dev

#elasticsearch #logstash #network

Responses(2)

Mike

Dec 1, 2021

Thank you for this! We have elastic cloud running on azure. For us to send our on-prem cisco syslog message to elastic do we do a logstash server on-prem that then forwards logs to elastic in azure? Thanks!

David Flores (aka: netpanda)

Network Automation Geek!

Sep 5, 2022

Sorry Mike, saw this way too late. I wonder if you manage to send your logs to Elastic Cloud?

Mr. Robot

Apr 26, 2020

This is good! Just wondering why not use something like: hub.docker.com/r/sebp/elk ? Any specific reason you went for separate containers?

David Flores (aka: netpanda)

Network Automation Geek!

Apr 27, 2020

It is a really good way try out the ELK stack for sure, but just wanted to show that with the official/default images you are able to build a lab environment to parse virtual devices logs.