Welcome to Sumo Logic's Community Content Repository!

We created this repository of content for everyone to use. Our goals are to help reduce time to value and shed light on possibilities. Your contributions are welcome.

DISCLAIMER

Please note the following before you use this content:

1. Support for this content is provided by our community on a volunteer basis. Visit the #sumo-content channel on our Public slack group @ http://slack.sumologic.com to discuss or ask for help. Submit GitHub Issues for bugs and enhancement requests.

2. This content is separate from our official app catalog unless otherwise noted; README files will indicate when specific content has been upgraded to official app status and is available in our app catalog and officially supported.

Table of contents

• Getting Started
• Contributing

Getting Started

• There are two types of content here

  • [Tools] : There's a tool for every occasion; from managing your collectors and data volume to processing rules, and everyones favorite: regular expressions.

  • [Content] : Content that helps extract instant value from a variety of data streams. This content typically includes pre-built dashboards, alerts, and extraction rules.

Contributing

Please review our contribution guidelines:

• Verify that all sensitive data has been removed BEFORE submitting a PR. This includes PII, Credentials, and Network data. Screenshots included.

• All application, dashboard and search content in .json format (exported from Sumo Logic). Please use a descriptive naming convention:

  • Company-Product-Function. E.g. AWS-Kinesis-Errors.json

• When possible, include a screenshot of your dashboards in .png or .jpg format. Name your screenshots the same as their respective .json content.

• Create README.md file within each subfolder to track:

  • Authors, versions, dates
  • Links to 3rd party docs that help setup the required data stream.

We follow the "fork-and-pull" Git workflow.

• Fork the repo on GitHub
• Clone the project to your own machine
• Commit changes to your own branch
• Push your work back up to your fork
• Submit a pull request so that we can review your changes

NOTE: Be sure to merge the latest from "upstream" before making a pull request!