Blue Herring Early Beta Users

Thanks for considering Blue Herring!

Hi everyone. I'm Mark W. Schumann, and you probably got to this survey from my or my company's LinkedIn page. The purpose of this survey is to get a few people involved in the early beta program for this new product.

If you don't know about the product, check out https://blueherring.io/beta-now/ for an overview.

Question Title

* 1. First off: do you manage or administer an IT operation?

No.

Yes, but it's a personal project or really small.

Yes. The system I run involves fewer than ten servers.

Yes. The system I run involves 11-100 servers.

Yes. The system I run involves more than 100 servers.

Question Title

* 2. Are you interested in participating in the early beta program of Blue Herring, a tool that continuously monitors changes in the configuration of resources like servers, APIs, DNS zones, and database schemas?

Yes!

Maybe, tell me more.

No.

Question Title

* 3. For lack of a better term, what's your technology vendor culture?

It's mostly a Microsoft .NET shop.

It's mostly a LAMP or Open Source oriented shop.

It's mostly an Apple shop.

It's mostly something else, like mainframe or IBM iSeries or special-purpose servers.

It's mixed, see comment.

Comments?

Question Title

* 4. What is your security stance?

It's kind of casual; we're teaching and experimenting and there are no live data of significance.

Security is of ordinary importance to us.

We handle commercial and personal data that require significant attention to security.

We are in a field that demands excellent security.

We cannot even consider a tool that hasn't been thoroughly vetted, including by prior users.

Question Title

* 5. How would you describe your requirement for configuration change monitoring? What types of things would you be monitoring and why are they relevant?

Question Title

* 6. When would you be ready to start working with Blue Herring?

Right now!

Within a few weeks.

First quarter 2021.

Later than first quarter 2021.

Not.

Question Title

* 7. What authority do you have in making the decision to commit to implementing Blue Herring or not? (Check all that apply. If none, leave this blank.)

I identify the needs.

I explore the options.

I make recommendations.

I make the commitment to use the technology.

I authorize the purchase order.

I'm above the person who authorizes the purchase order.

Question Title

* 8. If you found that Blue Herring fulfills a significant need in your enterprise, would you be willing to pay for licensing?

No. We only use free software.

No. This is not the type of solution we are willing to pay to use.

We are potentially open to using and paying for commercial software.

Question Title

* 9. Given that the Blue Herring product is really new, how much coordination and implementation help do you anticipate needing to get started with it?

If we can't do it all ourselves, we don't want it.

Reasonable documentation and some Slack chat should be good enough.

We expect to spend a couple of days with you getting Blue Herring set up and that's fine.

We expect that getting Blue Herring set up will be a little bit of a project and we'll want you (Mark) to work with us for a couple of weeks to make that happen.

Question Title

* 10. Any questions or comments on the product, the beta program, or anything related?

Question Title

* 11. This is great! Thanks for answering all those questions! Now I'm going to need some kind of contact information. Please fill in enough so I can reach back and have a conversation. Name and email or name and phone number are fine.