Sharing the Elastic <3

At Elastic, we <3 our community. As an open source company, our team extends beyond our employee base. In order to build products that best meet our users' needs, we focus and invest heavily in building a strong community, whether it's interacting around feature feedback on IRC and mailing lists, incorporating pull requests into our product releases, or swapping stories at meetups and events. We wouldn't be where we are today without you.

Here are all the places you can connect with us and your fellow users, plus places to find — and give — help.

Staying in Touch with Us

Global Community Groups

We have users all over the world sharing their experiences at Meetups, user groups, conferences and more. See our
International Communities section below to learn how to get connected on an event near you.

If you are interested in speaking at a local meetup or starting your own, we're here to help! Check out our
Meetups How-To page for more details.

You can also check out our
user group organizer's guide, intended to give you a full deep dive into everything around Elastic and User Groups. It's a bit long, but it's intended to be useful to everyone in our global community, from those who have never organized a meetup before to those who already do it monthly.

Social Media

Connect with us, 280 characters at a time. Follow us on Twitter
@elastic.

You can also give us a shout-out using any of these hashtags:
#elasticsearch, #logstash, #kibana, #elasticbeats, #elasticapm or #elasticxpack.

Blog

We publish numerous how-tos, feature deep dives, and post news updates on
our blog. Subscribe to our RSS feed for all the latest and greatest updates from Elastic land.

If you have a news item you'd like us to share or you're interested in authoring a guest blog post, let us know!

Using the Elastic Brand

You are welcome to use Elastic branding. Just make sure you conform to our brand guidelines.

All Things Code

Source Code

Elastic releases all of our open source projects under the
Apache 2.0 License. All code is hosted at GitHub and we love receiving contributions from our community, whether they are bug reports, feature requests, document improvements, or patches to the projects. Read on for more details about contributing.

Don't want to compile from source? No problem! You can find zip archives, tarballs, plus DEB and RPM packages on our
Downloads page.

Creating Plugins

While there are many plugins available for both
Elasticsearch, Logstash, and Kibana you may find you'd like to create your own. Here are some handy tips to help you get started.

Creating Beats

Beats is the platform for building lightweight, open source data shippers for many types of operational data you want to enrich with Logstash, search and analyze in Elasticsearch, and visualize in Kibana.

Documentation

We have extensive documentation for all of our products, including our language clients, various plugins for Elasticsearch and Logstash, and our Apache Hadoop connector.

We welcome and encourage contributions to improve our documentation. You can
check out the instructions to compile the documentation from source and submit improvements via a pull request, or just click on the edit button on any of our docs pages to submit a fix.

Even if you don't have a question to ask right now, if you're an IRC user come hang out with us!

Bug Reports

Issues can be filed on
GitHub Issues. (If you are not sure if you've uncovered a bug, please post a question to the appropriate forum category — see below — first.)

Feature Requests

File feature requests as
GitHub Issues. We discuss feature requests in the issue, so you're always up to date on the status of your request. If you're still thinking through what you'd like to request, please post a note in the forums (see below) to discuss the feature before filing an issue.

Discussion Forums

You can ask any questions about Elastic's entire product line and share your wisdom with your fellow users at http://discuss.elastic.co

If you prefer mailing list style communication to interacting with a web forum, you can still interact with our discussion boards solely via email. Just create your user account, set up your email preferences, then follow the instructions
here.

When asking questions about Elasticsearch, there are a few things you can do when posting your inquiry that will help people answer you quickly. Check out our
guidelines for posting a question to help you get started.

Don't see a group near you? No worries! We can help you start a meetup group, find a meetup group to give a talk at and help finding a venue for your user group. Visit our
Meetups How-To page for more information.

Japanese Community

Vietnamese Community

Is your group's information missing? Let us know so we can list it here.

Security Disclosures

Security Issues

We welcome vulnerability reports for all of our software. Please go to our vulnerability page for details on reporting a potential issue, and a list of resolved vulnerabilities.

Thanks

The Elasticsearch team thanks JetBrains for providing free licenses for PyCharm and IDEA. We have found PyCharm to be the best dedicated IDE for Python development. IntelliJ with the Python plugin can start quicker, but we like the full feature experience in PyCharm.

A lot of our team uses IDEA. Our developers really appreciate the refactoring support in IDEA. It includes some neat features like converting code to lambdas for Java 8 and suggesting to rename methods and constructors when you rename a field. It's also really good at making suggestions and does a good job of knowing what we are thinking and need.

We feel the IntelliJ team pays attention to details. We like all the ways to navigate code, power save mode, presenter mode, and how well other languages like Golang are supported.

We feel the git integration could be improved. We'd like to see better visualization of history and we have to run too many manual commands.