Announcing the dual releases of Shield 2.0.0-beta2 and Watcher 2.0.0-beta2, plugins for Elasticsearch with feature improvements.

<html><head></head><body>Today, we are happy to announce the releases of Shield and Watcher 2.0.0-beta2. These are the last planned beta releases before the 2.0.0 release candidates.

IMPORTANT: These are beta releases and are intended for testing purposes only. There is no guarantee that either Shield or Watcher 2.0.0-beta2 will be compatible with their respective 2.0.0 GA.

DO NOT DEPLOY IN PRODUCTION

<h3>Shield</h3>
This release comes with some exciting new features in Shield.

When it comes to securing your data in Elasticsearch, one of the more commonly requested features is the ability to define access control on documents and fields. With Shield 1.x, you could simulate document level security using a combination of filtered aliases and index level permissions per role. While this approach works for some cases, there are certainly cases where this becomes unmanageable (due to the number of aliases and roles one needs to define). Furthermore, it is not a bulletproof solution as it doesn&#x2019;t work for some of the APIs (e.g. parent/child searches), and it doesn&#x2019;t provide any form of field level security.

We are delighted to announce that Document and Field Level Access Control will be a first class feature in Shield 2.0 and is introduced in this beta2 release. What does being a &#x201C;first class feature&#x201D; mean? Well&#x2026; it is no longer bound to index aliases. Instead, you can define what documents and fields are accessible by role as part of the role definition. For field level access control you can now specify a list of accessible fields per index. For document level access control you can specify a query per index. These two together effectively create a filtered view of the index prior to any search executed by users with the relevant roles.

The following snippet shows what the configuration may look like as part of the role definition:

<div class="pre_wrapper" style="margin-bottom: 10px;">
	<pre class="programlisting prettyprint lang-yaml">us_customer_care:
 indices:
 &apos;help_desk&apos;:
 privileges: read
 query:
 term:
 country_code: us
 fields:
 - issue_id
 - description
 - customer_email
 - customer_address
 - customer_phone
	</pre>
</div>
With the above role definition, users with the us_customer_care role will only have read access to help desk issues for customers in the US, and this read access is limited to a 4 fields - issue_id, description, customer_email, customer_address and customer_phone. All other fields will be treated as non-existent for this user and attempting to search on those will yield no results.

You can read more about Document and Field level security <a href="https://www.elastic.co/guide/en/shield/2.0/setting-up-field-and-document-level-security.html">here</a>.


Another feature we&#x2019;ve added in this release is support for User Impersonation. With this support, it is now possible to enable a user to impersonate other users and by that execute requests on their behalf. User impersonation comes in handy when authentication is applied on the application level (outside of Elasticsearch/Shield), but the authorization should still be applied in Elasticsearch to ensure sensitive data is not compromised. Setting this &#x201C;run_as&#x201D; privilege is configured per role definition. As such, a best practice would be to create dedicated &#x201C;run_as&#x201D; roles for a set of impersonated users and assign this role to the relevant power users. The following snippet shows an example of such role:

<div class="pre_wrapper" style="margin-bottom: 10px;">
	<pre class="programlisting prettyprint lang-yaml">run_as_company_users: 
 run_as: *@company.com
	</pre>
</div>
The example above uses wildcards to defines a new role that enables users to impersonate any other user with a principal with @company.com suffix.

You can read more about user impersonation <a href="https://www.elastic.co/guide/en/shield/2.0/submitting-requests-for-other-users.html">here</a>.

Last but certainly not least, we&#x2019;re excited to announce that we&#x2019;ve opened up Shield for extensions. More specifically, you can now write a custom implementation of an authentication realm and plug it into Shield. If for any reason, you&#x2019;re forced to use an authentication mechanism that is not supported out-of-the-box by Shield, you can now write your own plugin just for the authentication part and still use all the other goodness Shield has to offer, including the extensive role-based access control over indices, document and fields, secured communication using SSL and IP filtering and of course the tightly integrated audit logging.

To read more about extending Shield realms, please read the <a href="https://www.elastic.co/guide/en/shield/2.0/custom-realms.html">documentation</a>. We&#x2019;ve also created an example custom realm <a href="https://github.com/elastic/shield-custom-realm-example">project</a> to serve as a reference.

<h3>Watcher</h3>
One of the more common requests for watcher was the ability to disable watches. Often users define watches to monitor different systems. But there comes a time when you want to consciously bring a system down for maintenance. The problem then is that the monitoring watches continue to execute periodically triggering notification about the monitored system being down. One way to work around this issue is to modify the watch schedule to some remote date in the future, such that it won&#x2019;t trigger for the duration of the system maintenance. But this is a wrong way to go about it. For this reason, we&#x2019;ve introduced a new in/active state to the watches, and with that, the ability to de/activate a watch. An inactive watch is a watch that is still stored/registered with watcher, but is never triggered. You can now proactively deactivate the monitoring watches and keep them inactive as long as you need. Once you&#x2019;re ready to continue monitoring your system, simply activate the monitoring watches. Read <a href="https://www.elastic.co/guide/en/watcher/2.0/watch-active-state.html">here</a> for more information about the in/active state of a watch.

In addition to the above we&#x2019;ve also added two new actions - hipchat and slack. If you or your organization uses either for internal communication, you can now send notifications to teams/rooms or to other users directly from watcher. In the spirit of watcher, all messages are templated, enabling sending detailed and rich messages. To read more about about these new actions please refer to <a href="https://www.elastic.co/guide/en/watcher/2.0/actions.html#actions-hipchat">HipChat Action</a> and <a href="https://www.elastic.co/guide/en/watcher/2.0/actions.html#actions-slack">Slack Action</a>. 

<h3>Closing Note</h3>
<code class="literal">2.0.0-beta2</code> introduces a wide range of new features in both Shield and Watcher. It also includes bug fixes and infrastructure enhancements in both products. Please refer to the release notes of <a href="https://www.elastic.co/guide/en/shield/2.0/release-notes.html#_2_0_0_beta2">Shield</a> and <a href="https://www.elastic.co/guide/en/watcher/2.0/release-notes.html#_2_0_0_beta2">Watcher</a> for a complete change list.

If you have any questions or want to share your experience with us and the community, don&apos;t by shy and use our dedicated forums:

<ul>
	<li>Shield Forum: <a href="https://discuss.elastic.co/c/shield">https://discuss.elastic.co/c/shield</a>
	</li>
	<li><a href="https://discuss.elastic.co/c/watcher"></a>Wather Forum: <a href="https://discuss.elastic.co/c/watcher">https://discuss.elastic.co/c/watcher</a></li>
</ul>
If you haven&apos;t tried either of these products yet, don&apos;t worry, it&apos;s not too late to start. You&apos;re welcome to visit the <a href="/downloads/shield">Shield</a> and <a href="/downloads/watcher">Watcher</a> download pages where you&apos;ll be presented with a simple and quick getting started guide.
</body></html>

shield-and-watcher-2-0-0-beta2-released.png

Shield and Watcher 2.0.0-beta2 released

<html><head></head><body>We&apos;re pleased to announce Watcher 1.0.0-Beta2!This release of Watcher includes bug fixes and enhancements to features introduced in Beta1.But we didn&#x2019;t stop there. Since the release of Beta1, we&#x2019;ve received wonderful feedback from all of you trying out Watcher. We&#x2019;re delighted with the activity in the <a href="https://discuss.elastic.co/c/watcher">forum</a>&#xA0;and I can honestly say that your questions have helped us improve Watcher in every aspect - functionality, usability and documentation.And yes, we are talking the talk and walking the walk. We took some of your wonderful suggestions and included them in this release. For more details, please read the <a href="https://www.elastic.co/guide/en/watcher/current/release-notes.html">release notes</a>.Installing Beta2 is as easy as it was installing Beta1. You can use the same beta key you received in the Beta1 registration email, but this time appending &#xA0;`-Beta2` to your key:bin/plugin -i elasticsearch/watcher/&lt;watcher-beta-key&gt;-Beta2Haven&#x2019;t registered yet? <a href="https://www.elastic.co/downloads/watcher">Do it now </a>and try Watcher out!</body></html>

Watcher Beta 2 - Fixes, Features, Feedback

Today we release the 1st public beta of Watcher, our commercial alerting & notification product. Like Shield, Watcher is a standalone Elasticsearch plugin.

<html><head></head><body>
Today we&#x2019;re delighted to release the first public beta of <a href="https://www.elastic.co/products/watcher">Watcher</a> &#x2013;&#xA0;our commercial alerting and notification product. In the same spirit of Shield, Watcher is a standalone plugin for Elasticsearch.
Elasticsearch enables you to extract invaluable knowledge and insights from changes in your data, in realtime. But with the fast moving markets we all operate in today, it is not enough. In order for you to stay ahead of the game, you also need to do something with that knowledge &#x2013;&#xA0;take actions that will directly translate to tangible values. And act fast. Act at realtime.
This is where Watcher complements Elasticsearch. While with Elasticsearch alone you need to be &#x201C;proactively proactive&#x201D; when it comes to analyzing your data, Watcher enables you to be &#x201C;reactively proactive.&#x201D; Hmm&#x2026; what?
Yes! With Elasticsearch alone you need to continually be there to run the analytics, interpret the results and act on them. With Watcher that is no longer the case. Watcher will monitor the data for you, act on the changes and/or notify you about important events &#x2013; freeing you up to focus on other important tasks, while letting you stay ahead of the game.
Here are a few examples of tasks you can define in Watcher:
<ul>
	<li dir="ltr">Watch indexed log events: Every 4 minutes, search for any errors that occurred in the last 5 minutes. Send me an email if more than 3 errors are found.</li>
	<li dir="ltr">Watch metrics data: Every 4 minutes, retrieve the average CPU usage over the last 5 minutes. Notify me when it goes above 75%. </li>
	<li dir="ltr">Watch indexed Tweets: Every minute, search for any mentions of earthquakes in the last 5 minutes. Notify me if more than 5 mentions are found in the same location.</li>
	<li dir="ltr">Watch incoming helpdesk events: Every 4 minutes, search for any new severity 1 tickets that were opened in the last 5 minutes. Use our pager service to notify me if any such tickets are found.</li>
</ul>Watcher was designed to serve all the scenarios above and many more. And we&#x2019;re very eager to see all the different use cases you use it for.
Next, I&#x2019;ll show how you&#x2019;d go about using Watcher. But first, if you haven&#x2019;t registered to the beta program, don&#x2019;t miss out and <a href="https://www.elastic.co/downloads/watcher">register now</a>.&#xA0;Once registered, you will receive the installation instructions by email, and as you will find out, installing Watcher is as easy as installing any other Elasticsearch plugin.
<h2 dir="ltr" style="line-height:1.38;margin-top:10pt;margin-bottom:0pt;">How do I work with Watcher?</h2> Watcher adds a new set of APIs to Elasticsearch to manage Watches. It&#x2019;s probably best to explain the concept of a Watch with an example. In this example, suppose you are indexing your web traffic logs in Elasticsearch. Let&apos;s first create a logs index and enable the _timestamp mappings, such that a timestamp will be associated with each log event that we&#x2019;ll index. 
<pre class="programlisting prettyprint lang-js" style="border:0">PUT logs
{
 &quot;mappings&quot; : {
 &quot;event&quot; : {
 &quot;_timestamp&quot; : { &quot;enabled&quot; : true }
 }
 }
}
</pre>Now that we have the logs index ready, let&#x2019;s add our first Watch. The immediate thing that comes to mind in this setup is the ability to pick up on errors in your logs as close to realtime as possible. In other words, you would like to watch newly indexed logs and look for any log events with an error status.
The following snippet registers a new watch that searches for any errors in the log entries in the last 5 minutes:
<pre class="programlisting prettyprint lang-js" style="border:0">PUT /_watcher/watch/error_status
{
 &quot;trigger&quot; : {
 &quot;schedule&quot; : { &quot;interval&quot; : &quot;5s&quot; }
 },
 &quot;input&quot; : {
 &quot;search&quot; : {
 &quot;request&quot; : {
 &quot;indices&quot; : [ &quot;logs&quot; ],
 &quot;body&quot; : {
 &quot;query&quot; : {
 &quot;filtered&quot; : {
 &quot;query&quot; : { &quot;match&quot; : { &quot;status&quot; : &quot;error&quot; }},
 &quot;filter&quot; : { &quot;range&quot; : { &quot;_timestamp&quot; : { &quot;from&quot; : &quot;now-5m&quot; }}}
 }
 }
 }
 }
 }
 }
}
</pre>If you look closer at the watch definition above, you&#x2019;ll see that we defined this watch with a schedule such that it will be executed every 5 seconds (I chose 5 seconds here just for the sake of the example, a more realistic value would have been 5 or 10 minutes).
The input loads data for the watch (what we like to refer to as payload). It does that by executing a search request over the logs index, and looks for events in the last 5 minutes with an &#x201C;error&#x201D; status.
Once this watch is added to Watcher, the schedule will immediately kick in and start ticking. Every 5 seconds the watch will execute and will search for errors. Although it looks like nothing is happening, in the background Watcher records all these executions in Watch History indices. And just like any other indices in Elasticsearch, you can explore them using the normal search API. Executing the following search request will return the last 10 watch executions:
<pre class="programlisting prettyprint lang-js" style="border:0">GET /.watch_history*/_search
{
 &quot;sort&quot; : [
 { &quot;execution_result.execution_time&quot; : &quot;desc&quot; }
 ]
}
</pre>OK&#x2026; Searching for errors and then searching the watch history is a good start, but that&#x2019;s just the beginning. It&#x2019;s very likely you want to do something with the search results - find out if any errors occurred, and if they did, do something about it. So let&#x2019;s change our watch to do exactly that:
<pre class="programlisting prettyprint lang-js" style="border:0">PUT /_watcher/watch/error_status
{
 &quot;trigger&quot; : {
 &quot;schedule&quot; : { &quot;interval&quot; : &quot;10s&quot; }
 },
 &quot;input&quot; : {
 &quot;search&quot; : {
 &quot;request&quot; : {
 &quot;indices&quot; : [ &quot;logs&quot; ],
 &quot;body&quot; : {
 &quot;query&quot; : {
 &quot;filtered&quot; : {
 &quot;query&quot; : { &quot;match&quot; : { &quot;status&quot; : &quot;error&quot; }},
 &quot;filter&quot; : { &quot;range&quot; : { &quot;_timestamp&quot; : { &quot;from&quot; : &quot;now-5m&quot; }}}
 }
 }
 }
 }
 }
 },
 &quot;condition&quot; : {
 &quot;compare&quot; : {
 &quot;ctx.payload.hits.total&quot; : { &quot;gt&quot; : 0 }
 }
 },
 &quot;actions&quot; : {
 &quot;log_event&quot; : {
 &quot;logging&quot; : {
 &quot;text&quot; : &quot;found {{ctx.payload.hits.total}} errors in the logs&quot;
 }
 }
 }
}
</pre>We added two new elements to our watch:&#xA0;a condition and actions. The condition is a check that is evaluated over the watch payload. In our case, the payload is the search results and the condition checks if any errors were found.
When the condition evaluates to true, the configured actions are executed. Here we defined a very simple logging action. This simple action logs text to the standard Elasticsearch logs (use the logging action at development time for testing and debugging).
You probably noticed that the logged text is actually a (Mustache) template, which allows us to include the number of hits in the log messages. As you learn more about Watcher you will see that many constructs in Watcher accept templates, making Watcher highly customizable.
Even now, after the watch was updated, the action is still not executing. The reason for this is simply because there are no log events with an error status. You can verify that the condition has not been met by simply searching the watch history for a watch record with a &#x201C;met&#x201D; condition that was executed in the last 5 seconds:
<pre class="programlisting prettyprint lang-js" style="border:0">GET /.watch_history*/_search
{
 &quot;query&quot; : {
 &quot;bool&quot; : {
 &quot;must&quot; : [
 { &quot;match&quot; : { &quot;execution_result.condition.met&quot; : true }},
 { &quot;range&quot; : { &quot;execution_result.execution_time&quot; : { &quot;from&quot; : &quot;now-5s&quot;}}}
 ]
 }
 }
}
</pre>Running the above will return no results. Now, let&#x2019;s put a new event, this time with an error status:
<pre class="programlisting prettyprint lang-js" style="border:0">POST /logs/event
{
 &quot;status&quot; : &quot;error&quot;
}
</pre>Within 5 seconds, you should see the log message in your Elasticsearch logs. If you search the watch history again, the results of the recent watch executions will be returned:
<pre class="programlisting prettyprint lang-js" style="border:0">GET /.watch_history*/_search
{
 &quot;query&quot; : {
 &quot;bool&quot; : {
 &quot;must&quot; : [
 { &quot;match&quot; : { &quot;execution_result.condition.met&quot; : true }},
 { &quot;range&quot; : { &quot;execution_result.execution_time&quot; : { &quot;from&quot; : &quot;now-10s&quot;}}}
 ]
 }
 }
}
</pre>Congrats! You&#x2019;ve successfully created your first Watch.
<h2 dir="ltr" style="line-height:1.38;margin-top:10pt;margin-bottom:0pt;">What&#x2019;s in a Watch?</h2> By now you probably have a good feeling what a Watch is. Each Watch has its own purpose and lifecycle, and its execution is defined by a well-defined set of constructs: Trigger, Input, Condition and Actions. Each of these constructs represents an abstraction with potentially many different implementations.
The goal with Watcher was to build a system that not only naturally integrates with Elasticsearch, but is also extensible and prepared to serve a vast variety of use cases &#x2013; from the simplest to the most complex requirements one might have. For the first public release we carefully chose an initial set of constructs that we believe will provide immediate value to you. You can view these constructs as the most basic building blocks for your watches:
<ul>
	<li dir="ltr">Schedule Trigger triggers the watches based on a schedule. Can be as simple as a fixed interval or more complex schedules based on cron expressions.</li>
	<li dir="ltr">Inputs load the initial payload for the condition to evaluate:</li>
	<ul>
		<li dir="ltr">search - Searches Elasticsearch, leveraging the full Elasticsearch query DSL capabilities</li>
		<li dir="ltr">http - Loads the data from an HTTP endpoint (making all Elasticsearch APIs accessible)</li>
		<li dir="ltr">simple - Static data that can be defined in the watch definition itself</li>
	</ul>
	<li dir="ltr">Conditions evaluate the loaded payload and determine whether the configured actions should be executed:</li>
	<ul>
		<li dir="ltr">always/never - Simple conditions that don&#x2019;t actually check anything but simply always evaluate to either true or false</li>
		<li dir="ltr">compare - Compares a value in the loaded payload to a given value (seen in the example above)</li>
		<li dir="ltr">script - Leverages Elasticsearch&#x2019;s scripting capabilities for more advance predicate logic</li>
	</ul>
	<li dir="ltr">Actions execute once the condition is met:</li>
	<ul>
		<li dir="ltr">email - Sends an email notification using your preferred SMTP service</li>
		<li dir="ltr">webhook - Notifies a 3rd party using a webhook (simple HTTP requests)</li>
		<li dir="ltr">index - Indexes the loaded payload back to Elasticsearch</li>
		<li dir="ltr">logging - Logs a message in the Elasticsearch logs (mostly used for development as seen above)</li>
	</ul>
</ul><h2 dir="ltr" style="line-height:1.38;margin-top:10pt;margin-bottom:0pt;">Where to now?</h2> As mentioned, if you haven&#x2019;t done so yet, you can register <a href="https://www.elastic.co/downloads/watcher">here</a>&#xA0;to get access to the beta program. We highly recommend you read the <a href="https://www.elastic.co/guide/en/watcher/current/index.html">online documentation</a>&#xA0;to learn more about Watcher and try it out. We&#x2019;re very curious to see how you are going to use it and what are you going to use it for, and we would absolutely love to get your feedback. For this we have set up a dedicated <a href="https://discuss.elastic.co/c/watcher">Watcher category</a>&#xA0;in our forums.
Happy watching!
</body></html>

Watcher Beta Goes Public! You Know, For Alerting...

Start free trial

Blog Footer CTA

Sign up for Elastic Cloud free trial

Founder and Engineer

Uri Boness

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_self">Terms of Service</a>, and you agree to receive the <a href="/legal/privacy-statement#how-we-use-the-information" target="_self">selected communications</a> at the contact details you provided above. See <a href="/legal/privacy-statement/" target="_self">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Communication Preferences - ONLY for /communication-preferences

제출하면 귀하가 <a href="/kr/legal/elastic-cloud-account-terms" target="_self">Elastic 서비스 약관</a>을 읽고 이에 동의하며, 위에 제공된 연락처로 <a href="/kr/legal/privacy-statement#how-we-use-the-information" target="_self">선택한 커뮤니케이션</a>을 수신하는 데 동의한 것으로 간주됩니다. 언제든지 수신을 거부할 수 있으며 자세한 내용은 <a href="/kr/legal/privacy-statement/" target="_self">Elastic 개인정보 취급방침</a>을 참조하시기 바랍니다.

By submitting you acknowledge that you've read and agree to our <a href="/legal/serverless-preview-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Serverless GDPR Text

제출하면 귀하가 Elastic <a href="/kr/legal/serverless-preview-terms" target="_self">서비스 약관</a>을 읽고 이에 동의하며, 위에 제공된 세부 정보를 사용하여 Elastic이 관련 제품 및 서비스에 대해 귀하에게 <a href="/kr/legal/privacy-statement#how-we-use-the-information" target="_self">연락할 수 있음</a>을 이해한 것으로 간주됩니다. 언제든지 수신을 거부할 수 있으며 자세한 내용은 <a href="/kr/legal/privacy-statement/" target="_self">Elastic 개인정보 취급방침</a>을 참조하시기 바랍니다.

By submitting you agree to <a href="/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud Terms of Service</a>. Your personal data will be processed in accordance with <a href="/legal/privacy-statement">Elastic's Privacy Statement</a>.

Cloud Trial GDPR Text

제출하면 <a href="/kr/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud 서비스 약관</a>에 동의하시게 됩니다. 개인 데이터는 <a href="/kr/legal/privacy-statement">Elastic의 개인정보 취급방침</a>에 따라 처리됩니다.

By submitting you acknowledge that you've read and agree to our <a href="/legal/terms-of-use" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Newsletter GDPR Text

제출하면 귀하가 Elastic <a href="/kr/legal/terms-of-use" target="_self">서비스 약관</a>을 읽고 이에 동의하며, 위에 제공된 세부 정보를 사용하여 Elastic이 관련 제품 및 서비스에 대해 귀하에게 <a href="/kr/legal/privacy-statement#how-we-use-the-information" target="_self">연락할 수 있음</a>을 이해한 것으로 간주됩니다. 언제든지 수신을 거부할 수 있으며 자세한 내용은 <a href="/kr/legal/privacy-statement/" target="_self">Elastic 개인정보 취급방침</a>을 참조하시기 바랍니다.

Explore similar demos

Overview

Speakers

Close

See more insights

The content on this page is not available in the selected language. As Elastic grows globally, we continue to support content in multiple languages.

The content on this page is not available in the selected language.

이 페이지의 콘텐츠는 선택하신 언어로 제공되지 않습니다. Elastic은 다양한 언어로 콘텐츠를 제공하기 위해 최선을 다하고 있습니다.조금만 더 기다려주세요!

Author

Articles by

Learn more

Watch now (no PT)

Watch now

See all top stories

All (no PT translation)

Contact information

Press Release

Share on Reddit

Share this story

Share by Email

Thank you for your interest!

Contact Info

Follow us on Youtube

Load More

Share on LinkedIn

Follow us on LinkedIn

Search Integrations

All Solutions

Video for

Follow us on Twitter

See when this webinar starts in my time zone

내 표준 시간대로 웨비나 시작 시간 확인하기

Register to Watch

Register now

See All Posts

Can't make it? Register and we'll send you the recording. You'll also receive an email with related content

참여가 어려우신가요? 등록하시면 녹화 자료를 보내드리겠습니다. 이메일로 관련 콘텐츠도 받아보실 수 있습니다.

Small image for

On-demand webinar

Featured webinar

Register to Attend

Share on Facebook

Reset all

Upcoming webinar

View more posts

Print

Hosted by

Sign In to Attend

View next

Follow us on Facebook

Share

Highlights

Read less

You'll also receive an email with related content

이메일을 통해 관련 내용을 보내드리겠습니다.

Thank you for registering. We will send you a confirmation email soon.

등록해 주셔서 감사합니다. 곧 확인 이메일을 보내드리겠습니다.

Author

Articles by Uri Boness

Founder and Engineer, Elastic

Shield and Watcher 2.0.0-beta2 released

Watcher Beta 2 - Fixes, Features, Feedback

Watcher Beta Goes Public! You Know, For Alerting...