Search company, investor...
Splunk company logo


Founded Year




Total Raised


Market Cap


Stock Price




About Splunk

Splunk (NASDAQ: SPLK) provides a software platform that enables organizations to gain operational intelligence. Its software collects and indexes data, regardless of format or source, and enables users to quickly and easily search, correlate, analyze, monitor, and report on this data. The company was founded in 2005 and is based in San Francisco, California.

Headquarters Location

270 Brannan Street 2nd Floor

San Francisco, California, 94107,

United States


Missing: Splunk's Product Demo & Case Studies

Promote your product offering to tech buyers.

Reach 1000s of buyers who use CB Insights to identify vendors, demo products, and make purchasing decisions.

Missing: Splunk's Product & Differentiators

Don’t let your products get skipped. Buyers use our vendor rankings to shortlist companies and drive requests for proposals (RFPs).

Expert Collections containing Splunk

Expert Collections are analyst-curated lists that highlight the companies you need to know in the most important technology spaces.

Splunk is included in 2 Expert Collections, including Conference Exhibitors.


Conference Exhibitors

5,302 items



163 items

These companies are featured in our Cybersecurity in Retail Tech Market Map report, published March 2021.

Splunk Patents

Splunk has filed 1453 patents.

The 3 most popular patent topics include:

  • Data management
  • Database management systems
  • Diagrams
patents chart

Application Date

Grant Date


Related Topics




Data management, Knowledge representation, Natural language processing, Biological databases, Information technology management


Application Date


Grant Date



Related Topics

Data management, Knowledge representation, Natural language processing, Biological databases, Information technology management



Latest Splunk News

Best practices for devops observability

Feb 7, 2023

Reseller News Best practices for devops observability Implement observability in strategic areas of the software development life cycle, especially with complicated microservices and cloud-native apps. Credit: Dreamstime My first blog post in 2005 was about application logging and I shared 10 practices I hoped my development team would follow. Today’s devops implementations around observability are more sophisticated and scalable, but several of my recommendations remain relevant, especially logging session IDs, specifying code-location details and ensuring logs are free from security and privacy-related data. Building observability best practices into the software development life cycle is critically important today because more apps deliver mission-critical customer and employee experiences. Devops teams should not be just concerned about faster mean time to resolve major incidents; they should ensure that apps and services are observable to continuously improve an experience’s robustness, reliability and ease of use. “The need for strong devops practices has never been felt so strongly,” says Arvind Jha, senior vice president, software development at Newgen. “With enterprises accelerating digital workflows and self-service options for customers, employees and partners, IT professionals are challenged to manage, maintain, secure and keep compliant thousands of applications.” Tame complex cloud-native apps and microservices with observability Today’s cloud-native applications are more complex than last generation’s two- and three-tier app architectures running in data centers. A single transaction may cross several microservices, query multiple databases, interact with third-party software as a service and run on multiple clouds. When application errors, poor performance and data issues impact user experiences, having centralised and meaningful information to discover root causes is key to resolving issues faster and fixing defects. What are some use cases where strong observability practices can impact operations? Identifying which microservices and APIs are causing performance bottlenecks Reviewing user inputs that cause application errors Tracing through a customer journey to identify where users are struggling Recognising when there’s a security breach and collecting forensics Pinpointing the source of data issues to be remedied with improved data validation Here are four observability best practices for devops teams building and supporting apps, microservices and databases. Seek business collaboration to optimise data collection Logging every JSON payload between all apps and services may seem like a good idea. But having too much data can slow down resolving issues, complicate finding root causes, or require expensive data science efforts to identify problem areas. How should devops teams decide what data is important to collect and how long to retain it? Anant Adya, executive vice president at Infosys Cobalt, suggests, “Agile development teams should closely collaborate with developer and stakeholder groups when managing devops observability tools to ensure alignment on goals. This will help teams avoid gathering and evaluating loads of data that don’t serve a specific purpose or drive a particular outcome.” The conversation with business stakeholders can help create a strategy and identify what user activities require higher service-level objectives. Developers must also understand what data is sensitive and either leave out or implement data masking before capturing it in logs, databases, or observability tools. Anand Krishnan, global head of pre-sales and solutions at Persistent Systems, recommends, “In observability, it’s about what to log, not just when and where. It’s important to stitch together different traces of a customer’s journey through different systems and applications and collate that in a central repository.” Centralising observability data can be daunting for large devops organisations. They may use application performance management (APM) tools and AIops platforms such as BigPanda, Datadog, Dynatrace, Moogsoft, New Relic, OpsRamp, or Splunk to centralise data, correlate alerts and monitor performance. Prashanth Samudrala, vice president of customer success at AutoRabit, shares several decision points where business stakeholders and technical leaders can provide valuable input on observability tools and data. He says, “Best practices include clearly defining metrics and goals centred around quality and overall productivity, running frequent scans for technical debt to understand key problems and flexing the team’s problem-solving muscle to learn and improve continuously.” Move beyond resolving production incidents Site reliability engineers (SREs), network operation centers (NOCs) and devops teams use application logs, infrastructure alerts and other telemetry data for incident management. They may use APM tools, IT service management (ITSM) platforms, automation capabilities and AIops solutions to resolve incidents and perform root cause analysis. But SREs and devops teams should be proactive and use observability data and tools to improve apps while developing and testing them. Tomas Kratky, founder and CEO of Manta, says, “Observability is part of quality assurance—the last mile needed to improve incident detection and simplify its resolution.” I recommend identifying the users and customers for observability data and tools. Self-organising teams should declare which developers, QA engineers, SREs and incident managers will become experts in using the tools, provide feedback to dev teams and be most responsible for improving quality when developing and testing software. Improving observability should be a key activity in a continuous testing strategy . Another best practice comes from Chris Cooney, developer advocate at Coralogix. “One approach to observability that has become ubiquitous amongst high-performing teams is full-stack observability, which enables teams to avoid the data silo,” he says. “Rather than settling for disparate observability data, with logs in one system, metrics in another and traces in a third, teams are rendering everything together.” Drive continuous improvement with observability A selected group of engineers may have the lead responsibilities around software quality, but they will need the full dev team to drive continuous improvements. David Ben Shabat, vice president of RD at Quali, recommends, “organisations should strive to create what I would call ‘visibility as a standard.’ This allows your team to embrace a culture of end-to-end responsibility and maintain a focus on continuous improvements to your product.” One way to address responsibility is by creating and following a standardised taxonomy and message format for logs and other observability data. Agile development teams should assign a teammate to review logs every sprint and add alerts for new error conditions. Ben Shabat adds, “Also, automate as many processes as possible while using logs and metrics as a gauge for successful performance.” Ashwin Rajeev, cofounder and CTO of Acceldata, agrees automation is key to driving observable applications and services. He says, “Modern devops observability solutions integrate with CI/CD tools, analyse all relevant data sources, use automation to provide actionable insights and provide real-time recommendations." Coordinate monitoring and observability practices Historically, monitoring tools were more likely to be instrumented by NOCs or ITSM and other IT ops teams, whereas observability practices stemmed from developers looking to centralise application log files and use them to resolve defects and address performance issues. Today, devops teams bring these capabilities together and develop a holistic approach to observing and monitoring customer journeys and employee experiences. Krishnan says unifying alerts and monitoring is an important step. “Previously, you could alert an engineer about a systems issue by sending an email or doing a core dump. Today it’s about integrating it into the developer ecosystem and production support systems,” he says. Devops teams want to release frequently and address production issues quickly. Investing in observability helps find issues before they reach production and provides the forensics to discover hard-to-find problems.

Splunk Frequently Asked Questions (FAQ)

  • When was Splunk founded?

    Splunk was founded in 2005.

  • Where is Splunk's headquarters?

    Splunk's headquarters is located at 270 Brannan Street, San Francisco.

  • What is Splunk's latest funding round?

    Splunk's latest funding round is PIPE - III.

  • How much did Splunk raise?

    Splunk raised a total of $40M.

  • Who are the investors of Splunk?

    Investors of Splunk include Starboard Value, Hellman & Friedman, Silver Lake, Sevin Rosen Funds, August Capital and 8 more.

  • Who are Splunk's competitors?

    Competitors of Splunk include Micro Focus, VuNet, Cydarm Technologies, Zebrium, TINES, Baselime, Devo Technology, Coralogix, Cribl, Securonix and 38 more.

Compare Splunk to Competitors

Securonix Logo

Securonix provides enterprises with a security analytics platform that uses Hadoop and machine learning technology to consume, enrich and analyze massive volumes of data to detect and prioritize the highest insider threat, cyber threat, cloud, and fraud attacks automatically and accurately. The company was founded in 2017 and is based in Addison, TX.

Exabeam Logo

Exabeam complements existing security information and event management and log management systems with machine-learning technology that focuses on attacker behavior rather than malware and tools to detect modern cyberattacks. Exabeam's user behavior analytics solution leverages existing log data to quickly detect advanced attacks, prioritize incidents and guide effective response. The company's Stateful User Tracking automates the work of security analysts by resolving individual security events and behavioral anomalies into a complete attack chain. The firm primarily serves retail banks, investment banks, academic institutions, retail, and technology firms. It was founded in 2013 and is based in Foster city, California. Logo offers a cloud-based service that enables companies to process the diagnostics data they collect about their applications.

LogRhythm Logo

LogRhythm, a provider in security intelligence and analytics, empowers organizations around the globe to rapidly detect, respond to and neutralize damaging cyber threats. The company's platform unifies next-generation SIEM, log management, network and endpoint monitoring, and advanced security analytics. In addition to protecting customers from the risks associated with cyber threats, LogRhythm provides unparalleled compliance automation and assurance, and enhanced IT intelligence.

Stellar Cyber Logo
Stellar Cyber

Stellar Cyber is a security analytics provider that has created Starlight, a unified security analytics platform designed to be the SOC Command Center for pervasive data collection, breach detection, investigation and response (CDIR). The company's customers are mid-tier and large enterprises and service providers building managed detection and response services for those who don't have in house incident responders.

Coralogix Logo

Coralogix provides an ML-powered log analytics platform that allows DevOps teams to autonomously manage and analyze log data in cloud applications. Engineers can narrow down hundreds of millions of logs to suspected logs, broken flows, error trends, and problematic version upgrades in order to reach time to market fast, avoid customer attrition, and accelerate their version delivery without compromising quality or stability. Coralogix allows DevOps and other engineering teams a way to observe and analyze data streams before they get indexed and/or sent to storage, giving them more flexibility to query the data in different ways and glean more insights faster. Coralogix was founded in 2014 and is based in San Francisco, California.

Discover the right solution for your team

The CB Insights tech market intelligence platform analyzes millions of data points on vendors, products, partnerships, and patents to help your team find their next technology solution.

Request a demo

CBI websites generally use certain cookies to enable better interactions with our sites and services. Use of these cookies, which may be stored on your device, permits us to improve and customize your experience. You can read more about your cookie choices at our privacy policy here. By continuing to use this site you are consenting to these choices.