highlight / highlight Goto Github PK

highlight.io: The open source, full-stack monitoring platform. Error monitoring, session replay, logging, distributed tracing, and more.

Home Page: https://app.highlight.io

License: Other

Go 14.27% JavaScript 7.34% HTML 0.27% TypeScript 73.57% Makefile 0.03% SCSS 0.75% Python 0.81% CSS 1.28% Less 0.01% Shell 0.05% Dockerfile 0.04% EJS 0.02% Ruby 0.23% Java 1.13% MDX 0.01% ANTLR 0.01% Rust 0.15% C# 0.06%

apm golang metrics monitoring observability open-source self-hosted session-replay typescript full-stack

highlight's Introduction

Docs - Community (Support & Feedback) - Feature request - Bug report

highlight.io: The open-source, fullstack monitoring platform.

highlight.io is a monitoring tool for the next generation of developers (like you!). Unlike the age-old, outdated tools out there, we aim to build a cohesive, modern and fully-featured monitoring solution, something we wished WE had. And it's all open source :)

At a high level, highlight.io's feature set is:

Session Replay
Error Monitoring
Logging

We strive to make highlight.io as easy to install as a few lines of code in any environment.

Read more about our features, values and mission below, and get started at https://highlight.io today!

Get started for free
Features
SDKs
Contributors
Mission
Values

Get started

Hosted highlight.io (free to get started!)

The fastest and most reliable way to get started with highlight.io is signing up for free at app.highlight.io. After making an account, getting started is as easy as installing the client SDK snippet.

Hobby self-hosted

Deploy a hobby instance in one line on Linux with Docker (we recommend at least 8GB of RAM, 4 CPUs, and 64 GB of disk space):

git clone --recurse-submodules https://github.com/highlight/highlight
# or `git submodule update --init --recursive` on git < 2.13
cd docker && ./run-hobby.sh

After a brief frontend load time, the app should be accessible at https://localhost

Good for <10k sessions and <50k errors ingested monthly. See our docs for more info and limitations.

Enterprise self-hosted

See our enterprise self-hosted docs to deploy a scalable, production-ready instance with support from our team.

Features

Session Replay: Understand WHY bugs happen.

Dom-based High-fidelity Replay: Replay every interaction and dom change that happened in a given browser session (powered by https://github.com/rrweb-io/rrweb)
Outgoing Network Requests: See all the network requests (and their contents) in a given session to reproduce the data that was sent/received by your frontend -> docs
Console logs: Analyze the logs printed (console.error, console.log, etc..) to the console from your frontend -> docs
Embedded Error Monitoring: See the errors associated with a given session to understand what the user was doing leading up to them.
Session Comments: Comment on errors to communicate with your team on user frustration, bugs, and more! -> docs
Integrations with your favorite tools -> docs

Error Monitoring: Understand WHAT bugs are happening.

Customizable Error Grouping: Customize rules for grouping repeated errors -> docs
Customizable Alerting Rules: Customize how often, and where alerts are sent -> docs
Embedded Session Replay: See all of the sessions associated with any given error.
SDK Support: Support for a long (and growing!) list of SDKs.
Integrations with your favorite tools -> docs

Logs: Dig deeper into what's happening on your server.

Powerful Search: Search across all your logs, with automatic property collection -> docs
Log Alerts: Set thresholds for your log alerts, and view them in the alerts dashboard -> docs
Embedded Session Replay and Errors: See all of the sessions & errors associated to a log.
SDK Support: Support for a long (and growing!) list of SDKs.
Integrations with your favorite tools -> docs

Traces: Track the performance of operations on your server.

Powerful Search: Search across all your traces, with automatic property collection -> docs
Log Alerts: Set thresholds for your log alerts, and view them in the alerts dashboard -> docs
Embedded Session Replay, Errors and Logs: See all of the sessions, errors, and logs associated to a trace.
SDK Support: Support for a long (and growing!) list of SDKs.
Integrations with your favorite tools -> docs

More?! Metrics? Traces? Merch?

Have an idea for what we should build next? Please share our community or via a Github Issue!

Read a full list of highlight.io features.

SDKs

All of our SDKs for highlight.io can be found in the sdk directory. To get started with these SDKs, we recommend the getting started guide in our docs.

Contributors

_{Jay Khatri} 💻 📖	_{Vadim Korolik} 💻 📖	_{Zane Mayberry} 💻 📖	_{Eric Thomas} 💻 📖	_{Chris Schmitz} 💻 📖	_{Chris Esplin} 💻 📖	_{Spencer Amarantides} 💻 📖
_{Abhishek More} 💻	_Aaron 💻	_{Julian Schneider} 🎨	_{Cameron Brill} 💻	_{Sasha Aptlin} 💻	_{Richard Hua} 💻	_{Anthony Teo} 💻
_{Nathan Brockway} 💻	_{John Pham} 💻	_{Lewis Liu} 💻	_Darius 💻	_{George Thayamkery} 💻	_{Betty Alagwu} 💻	_{Aaron Carver} 💻
_{Nathan R} 💻	_denise 💻	_{Xiaojing Chen} 💻	_{Shayne O'Sullivan} 💻	_{Nils Gereke} 💻 📖	_{Nir Gazit} 💻	_{Jayant Keswani} 💻
_wancup 📖	_{Adam from Buildjet} 💻	_{Nick Fiacco} 💻 📖	_{Mark Chapman} 📖	_edde746 💻	_{Lucas Lemanowicz} 💻	_{Karl Horky} 📖
_{Pedro Saratscheff} 💻	_{Grant Mercer} 📖	_Lewis 📖	_{Kalkidan Betre} 💻	_{Tolulope Adetula} 💻	_jemiluv8 💻	_{Gergő Móricz} 💻

Our Mission

Our mission is to support developers like you in shipping with confidence. We do this by giving you the tools you need to uncover, resolve, and prevent issues in your web app.

Our Values

We build in public.

We strive to build in public in every way we can. This means that what we built, what we're building, and what we plan to build is shared with the world.

We build a cohesive product.

People may think that we're building multiple products (session replay, error monitoring, etc..). But we see it as one. Before we build anything new, we prioritize making it operate seemlessly with everything else.

We build for today's developer.

If you're building software, why should you care about grafana or loki or the elk stack? highlight.io is built for developers that want to develop. Leave the monitoring stuff to us 👍.

highlight's People

Contributors

Stargazers

Watchers

Forkers

lewisl9029 aerissolutions mindkhichdi mysticaltech thearchiver saratscheff shivamsinha15 mrcodechef ngloader anhgeeky dejan-stankovic minhtran83 cyberflamego rgrieselhuber arunpraba jithinraj hirajanwin diki gregvarghese jrcribb dmoena haversham94 nanderoo frikadellios cca313 nirga miapolis weblfe cutlope digksskawk01 mp-04 nicholasfields pspglb deltaepsilon archiveproject betty-alagwu lucaslemanowicz bejewel-kyoungmin d29107d benmorehouse appdirectory rayyanq edde746 deluxeowl snawar92 sanjusudheerm fwouts manogna7 ray-56 saksham294 billmcglynnokon shayneo germavinsmoke d-lite hefeweizen anietieakpan enixdark spread0x maheskrishnan traviscooper nagyist xiayu1028 hujing1113 michiko5173 chief-fei parkerproject biztrology-kd zipdevil skywolfdreamer smw faceless28 tormelo-software nfiacco mozinator convivitybackendteam lewisl001 shivam-bit valdo99 thecmdrunner aggmoulik tyldev jstuve thinkafterbefore abhicareers meiseayoung daggerhub syntaf wancup lexciobotariu bahdcoder solomonfrank jumalaw98 octaviookumu nev1ne kolabank ankur-datta-4 jolzyfx giftade jay-khatri pratik-mogal

highlight's Issues

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

hello

another programattic test

Testing body

Convert our stack to use docker

This is super important, especially as we prepare for having an on premise solution.

Enable "jump to time" in the player

From the console, network and event stream, we should have buttons that let the user jump to a specific time in the playback.

On the actions/timestamps on the sidebar, we want to let the user go to that specific timeistamp in the player. Same goes for network resources and console message.

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

another programattic test

Testing body

another programattic test

Testing body

Broadcast Highlight (plus ⭐️): Modal in the app + links to repo in the app and landing page

Convert our stack to use docker

This is super important, especially as we prepare for having an on premise solution.

testing

Title

Description

Anonymize session data as a recording setting

another programattic test

Testing body

Preserve console output styling from dev tools

another programattic test

Testing body

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

Convert our stack to use docker

This is super important, especially as we prepare for having an on premise solution.

Get rid of firebase (at least for self-hosted)

Convert our stack to use docker

This is super important, especially as we prepare for having an on premise solution.

another programattic test

Testing body

Convert our stack to use docker

This is super important, especially as we prepare for having an on premise solution.

Support sessions across page reloads.

Right now, for every page reload, a new session is started and these sessions are show individually in the UI.

For single page apps, this is mostly fine. But for server side rendered apps, this generates a shit ton of sessions, so needs to be fixed.

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

![image.png](https://uploads.linear.app/56bcb1e5-92b5-4fad-b2c1-bb6738442711/a653ceec-b26c-4e7f-b1e5-a1b78909a07d/image.png "image.png")

Support sessions across page reloads.

Right now, for every page reload, a new session is started and these sessions are show individually in the UI.

For single page apps, this is mostly fine. But for server side rendered apps, this generates a shit ton of sessions, so needs to be fixed.

another programattic test

Testing body

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

Look into how to support live recording

We'll have to have some sort of polling strategy in postgres in order to enable live recording. We could use a subscription on the frontend and grab events as they come on the other end.

I imagine this being a pretty big feature, and could even be a sales enablement tool (i.e. when a high value customer comes in, you get a notification when they're live)

Testing

testing

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

another programattic test

Testing body

Preserve console output styling from dev tools

Right now, we collect the contents of a the console message in the console, but its just text. Ideally, we can reproduce everything, something like this:

another programattic test

Testing body

hello

errors feed caching causes incorrect instance/user counts to show in the feed

Describe the bug
errors feed caching causes incorrect instance/user counts to show in the feed

To Reproduce
Steps to reproduce the behavior:

visit https://app.highlight.io/errors
click an error in the feed
visit page 2 of the feed
click some errors in the feed
visit page 1 of the feed
click some errors in the feed, and see that the instance/user counts in the left feed preview change upon clicking

Additional context
Likely due to apollo caching data between GetErrorsOpenSearch and GetErrorGroup, and using an incorrect cache key?

highlight / highlight Goto Github PK

highlight's Introduction

highlight.io: The open-source, fullstack monitoring platform.

Table of Contents

Get started

Hosted highlight.io (free to get started!)

Hobby self-hosted

Enterprise self-hosted

Features

Session Replay: Understand WHY bugs happen.

Error Monitoring: Understand WHAT bugs are happening.

Logs: Dig deeper into what's happening on your server.

Traces: Track the performance of operations on your server.

More?! Metrics? Traces? Merch?

SDKs

Contributors

Our Mission

Our Values

We build in public.

We build a cohesive product.

We build for today's developer.

highlight's People

Contributors

Stargazers

Watchers

Forkers

highlight's Issues

Recommend Projects

Recommend Topics

Recommend Org