# Consultaton Services

**URL:** <https://discuss.elastic.co/t/consultaton-services/74257>\
**Category:** Elasticsearch\
**Created:** [February 7, 2017, 5:26pm UTC](https://discuss.elastic.co/t/consultaton-services/74257 "2017-02-07T17:26:35Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![BrianAnderson](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@BrianAnderson](https://discuss.elastic.co/u/BrianAnderson)\
**Post date:** [February 7, 2017, 5:26pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/1 "2017-02-07T17:26:35Z")

</div>

Interested in ElasticSearch Consultation Services links. Contact form on Elasticsearch website would not submit.

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [February 7, 2017, 5:43pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/2 "2017-02-07T17:43:06Z")

</div>

Send an email to [sales@elastic.co](mailto:sales@elastic.co) to get that information?

---

<div class="post-metadata">

**Author:** ![geena.rollins](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geena.rollins/32/15661_2.png) [@geena.rollins](https://discuss.elastic.co/u/geena.rollins)\
**Post date:** [February 19, 2017, 6:53pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/3 "2017-02-19T18:53:28Z")

</div>

Hi Brian,

After internal Elasticsearch consulting for three years at Symantec, I recently started a sole proprietorship to be an independent Elasticsearch consulting architect.

I'd love to help your team with ...

- Product Development with Elasticsearch
- Site-Reliability Engineering for Elasticsearch
- Elasticsearch Ecosystem
- Good choices for your Use Cases

Best wishes.....Geena  
[leapfire.com](http://leapfire.com)  
in/rollins

---

<div class="post-metadata">

**Author:** ![BrianAnderson](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@BrianAnderson](https://discuss.elastic.co/u/BrianAnderson)\
**Post date:** [February 21, 2017, 4:28pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/4 "2017-02-21T16:28:50Z")

</div>

For the time, I gave up on configuring our local service and have attempted to start a trial of ElasticCloud. I still am not able to get past provisioning a cluster. When I attempt to click on my Elastic endpoint or my Kibana endpoint after following video tutorials I am confronted by a login process. None of the credentials I set up yet work at all. It is also not clear where to set up a new user name. When you go into Kibana configuration and reset the password it does so, and shows the password, but nowhere does it display the proper username to use. I could begin by reading the documentation from top to bottom, but it is curious that the tutorials should skip this crucial info.

---

<div class="post-metadata">

**Author:** ![softwaredoug](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/softwaredoug/32/22681_2.png) [@softwaredoug](https://discuss.elastic.co/u/softwaredoug)\
**Post date:** [February 21, 2017, 4:57pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/5 "2017-02-21T16:57:52Z")

</div>

Hi, our firm OpenSource Connections ([http://opensourceconnections.com](http://opensourceconnections.com)) has  
done open source search consulting (Solr then Elasticsearch) for 10 years.  
Don't hesitate to reach out to me via [dturnbull@opensourceconnections.com](mailto:dturnbull@opensourceconnections.com)

Other firms I might recommend include Flax ([http://flax.co.uk](http://flax.co.uk)) and Sematext  
([http://sematext.com](http://sematext.com)). Both firms have been around about as long, and each  
of us has slightly different competencies.

I actually have a Solr/ES consulting buying guide you might find useful,  
shoot me an email and I'll send it to you.

Best  
-Doug

---

<div class="post-metadata">

**Author:** ![Paul\_Coghlan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_coghlan/32/15249_2.png) [@Paul\_Coghlan](https://discuss.elastic.co/u/Paul_Coghlan)\
**Post date:** [February 21, 2017, 5:41pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/6 "2017-02-21T17:41:55Z")

</div>

Hi Brian,

The username is the email that you would have signed-up with when you first joined (see screenshot below):

 ![](https://us1.discourse-cdn.com/elastic/original/2X/c/c59fcb01cce76bb81689b054fe1fd7e86ac25947.png)

Does that work with your password?

Kind regards,

Paul Coghlan

---

<div class="post-metadata">

**Author:** ![BrianAnderson](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@BrianAnderson](https://discuss.elastic.co/u/BrianAnderson)\
**Post date:** [February 21, 2017, 6:01pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/7 "2017-02-21T18:01:03Z")

</div>

Actually, it isn't that. It is simply "Elastic", and for Kibana it is "Kibana".

---

<div class="post-metadata">

**Author:** ![Paul\_Coghlan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/paul_coghlan/32/15249_2.png) [@Paul\_Coghlan](https://discuss.elastic.co/u/Paul_Coghlan)\
**Post date:** [February 21, 2017, 6:05pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/8 "2017-02-21T18:05:28Z")

</div>

Ah - apologies - I mis-read your question. So are you able to login to both Elastic and Kibana now?

---

<div class="post-metadata">

**Author:** ![BrianAnderson](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@BrianAnderson](https://discuss.elastic.co/u/BrianAnderson)\
**Post date:** [February 21, 2017, 6:07pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/9 "2017-02-21T18:07:01Z")

</div>

Yes, thank you!

---

<div class="post-metadata">

**Author:** ![geena.rollins](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geena.rollins/32/15661_2.png) [@geena.rollins](https://discuss.elastic.co/u/geena.rollins)\
**Post date:** [February 21, 2017, 9:13pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/10 "2017-02-21T21:13:14Z")

</div>

Brian, you've identified a common problem. There is so much documentation that applies to so many different use cases, it is hard to know what the best approaches are for your particular use case. I like helping clients to accelerate up the learning curve and become self sufficient.

As for experience, Elasticsearch 1.0 came out in February 2014, so we all have about 3 years of experience. I've been a search engineer for about 18 years using various technologies.

Leapfire distinguishes itself in several ways. I do not need a big contract; I am satisfied with an engagement as short as 4 hours. You always work with the principal. I have a closer relationship with Elastic than any of the big consulting firms. I formulated my business plan through discussions with Elastic sales reps. Leapfire and Elastic have no points of competition and we are fully complementary.

Elastic asks [“How did Geena become so knowledgeable of Elasticsearch?”](https://www.elastic.co/blog/elasticsearch-support-an-investment-that-keeps-paying-off-at-symantec)

If you would like to explore running Elasticsearch with your own operations staff, let me know. I've setup more than a dozen clusters over the years for 1.x, 2.x, and 5.x. And I'll train them for Elasticsearch Site Reliability.

...Geena

_"My heart is in the work."_ -- Andrew Carnegie

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 21, 2017, 9:13pm UTC](https://discuss.elastic.co/t/consultaton-services/74257/11 "2017-03-21T21:13:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
