Grafana Labs Observability Survey

Tiedostoa ei voi avata, koska JavaScript ei ole käytössä selaimessa. Ota se käyttöön ja lataa sivu uudelleen.

We want to hear from you about your observability practice! The survey should take about 5 minutes. All responses will be kept anonymous.

How many different observability (logs/metrics/traces) technologies (e.g., Grafana, Prometheus, Grafana Mimir, Grafana Loki, Datadog, New Relic, Splunk, ELK) do you/your specific group use? *

2-3

4-5

6-7

8-10

11-20

21-50

51-100

101+

Don't know

How many different observability (logs/metrics/traces) technologies (e.g., Grafana, Prometheus, Grafana Mimir, Grafana Loki, Datadog, New Relic, Splunk, ELK) does your entire company use?

2-3

4-5

6-7

8-10

11-20

21-50

51-100

101+

Don't know

What observability technologies are used in your group? (Choose all that apply.)

AppDynamics

Chronosphere

Cortex

Datadog

Dynatrace

Elastic/ELK

Grafana

Grafana Loki

Grafana Mimir

Grafana Pyroscope

Grafana Tempo

Honeycomb

InfluxDB

Jaeger

M3DB

New Relic

OpenSearch

OpenTelemetry

Polar Signals

Prometheus

Splunk

Thanos

VictoriaMetrics

Muu:

Pakollinen

How many data sources do you/your group have configured in Grafana and actively use? *

0. We're just getting started.

2-3

4-5

6-7

8-10

11-20

21-50

51-100

101+

N/A. We don’t use Grafana. (What?! Seriously?)

Do you correlate your operations/infrastructure data with data relevant to any of these departments in your organization? (Choose all that apply.)

Engineering/software development

Sales

Support

Marketing

Finance

N/A. We don't correlate our data with other departments yet.

Muu:

Pakollinen

What value do you get out of correlating different types of data? (Choose all that apply.) *

Cost control

Profitability and margin calculation

Unit cost

Capacity planning

Resource efficiency

Improved user experience

Higher customer retention

N/A. We don't correlate our data in this manner yet.

Muu:

Pakollinen

Which of these statements best describes your organization's approach to observability? *

There's a central operator group that manages the observability platform on behalf of other engineering teams.

Every engineering team is responsible for standing up their own observability platform and instrumenting their own services.

We have a team supporting other teams, like internal consultants/integrators.

We don't do it, or are just starting to explore observability in production.

If your organization has centralized observability, has that led to time/cost savings? *

Yes

N/A. We don’t centralize observability.

If your organization has achieved cost/time savings from centralized observability, please tell us more about the results (MTTR improvements, reduction in overhead, increased adoption, etc.).

Are you using observability tools under an open source or a commercial license?

Open source only

Mostly open source

Roughly equal: open source and commercial

Mostly commercial

Commercial only

Which best describes your observability setup? *

SaaS only

Mostly SaaS

Roughly equal: SaaS and on-premises

Mostly on-premises

On-premises only

What industry is your organization in? *

Applied Sciences

Automotive & Manufacturing

Energy & Utilities

Financial Services

Government

Healthcare

IoT

Media & Entertainment

Retail/E-commerce

Software & Technology

Telecommunications

Travel & Transportation

Muu:

What is the size of your organization? *

10 or fewer employees

11 - 100 employees

101 - 500 employees

501 - 1,000 employees

1,001 - 2,500 employees

2,501 - 5,000 employees

5,001+ employees

What region are you based in? *

Africa

Asia

Europe

Middle East

North America

Oceania

South America

Which best describes the maturity of your organization's current observability efforts? *

Reactive: Customers are bringing you problems before you know about them. Time is spent responding to issues reported by users.

Proactive: You work to develop procedures and implement tools to know about issues before your users do. You are able to prevent issues from impacting customers some of the time.

Systematic: You develop procedures and implement tools to know about issues before your users do, and are able to minimize impact to users. Observability and performance testing are implemented early in the SDLC, preventing issues from occurring in production.

Which of the following potential AI/ML-powered features would be most valuable to you for your observability practice? *

Query assistance

Dashboard generator

Automated incident summary

Anomaly detection

Predictive insights

None of the above. It's mostly hype.

Muu:

Pakollinen

How much have you invested in OpenTelemetry? *

We are not using it at all.

We are investigating it.

We are using it in production.

We are using it extensively.

We are using it exclusively.

How does your OpenTelemetry usage today compare to a year ago? *

The same

Less

Don’t know

How much have you invested in Prometheus? *

We are not using it at all.

We are investigating it.

We are using it in production.

We are using it extensively.

We are using it exclusively.

How does your Prometheus usage today compare to a year ago? *

The same

Less

Don’t know

How relevant are these observability use cases to you? (Please check one box per row.) *

Not on our radar

Starting to talk about it

Building POCs

Actively doing in production

Don't know

SLOs/SLIs

Observability of AI systems and LLMs

Using eBPF or Cilium for deeper kernel-level observability

Combining application performance observability into our overall observability efforts

Observing event-driven microservices and saga patterns

Observing software supply chain securit

For these same observability use cases, are they more or less relevant to you today compared to last year?
(Please check one box per row.)
*

More relevant

The same

Less relevant

Don't know

SLOs/SLIs

Observability of AI systems and LLMs

Using eBPF or Cilium for deeper kernel-level observability

Combining application performance observability into our overall observability efforts

Observing event-driven microservices and saga patterns

Observing software supply chain security

What are your biggest concerns about observability? (Choose all that apply.) *

Cardinality

Visibility into resource usage

Cost

Unpredictable bills

More noise; signal-to-noise challenge

Complexity of managing systems

Vendor lock-in

Data retention time

Convincing management of the value

Muu:

Pakollinen

What are you most excited about in the observability space?

Thank you for completing this survey! Would you like to have even greater impact on the report (and get some cool swag too)? We are looking for respondents to do more in-depth interviews. All answers will be anonymized in the final report. If you're interested, please write your name and email address below, and we will be in touch.

Lähetä

Tyhjennä lomake

Älä koskaan lähetä salasanaa Google Formsin kautta.

Forms

Tämä lomake luotiin verkkotunnuksessa Grafana Labs.