devneelpatel

OneUptime (https://oneuptime.com) | Remote | Full Time | Sr Full Stack Engineers + LLM/ML Engineer

We're building an open-source alternative to Datadog.

Tech Stack: TypeScript + React + Node + Clickhouse + Postgres

OneUptime.com already does it with the copilot feature. It also fixes exceptions, add structured logs, optimizes functions / spans that take a long time to complete and integrates with OpenTelemetry natively.

It's also 100% open-source.

This is exactly what we do at OneUptime.com. Show you AI generated possible Incident remediation based on your data + telemetry + code. All of this is 100% open-source.

This is amazing! always been a huge fan of nostr.

Will def do. Please do self-host and let us know your feedback.

Thank you for the feedback. 1. We're consolidating so many containers into 1. This is along project but a PR is open for it. 2. Monitors and Status Page are two distinct concepts. You create a monitor and then add the created monitor to the Status Page. Maybe we should make this clearer. 3. Currently being actively worked on. More updates end of Q2. 4. <3 5. We got the same feedback from some of our customers. This is on our roadmap. 6. This is fixed.

OneUptime.com does this for you and is 100% open-source.

100% of what OneUptime does is FOSS and always will be. We dont believe in open-core.

Maybe its blocking tailwind files. Let me fix this. Ty for reporting.

No, and never will be.

100% of what we do is FOSS.

We have Incoming Request monitor for this. OR you can deploy custom probes in your private network. https://oneuptime.com/docs/probe/custom-probe

Kuberetes integration is coming soon. Its on our roadmap.

You dont have to host it if you dont want to, we have a SaaS service as well at https://oneuptime.com

Oddly enough, this is why we started OneUptime in the first place. We were burned by the DataDog bill and wanted an open source observability platform ourselves.

Some of the differences are:

Grafana started as visualization tool and has now decoupled multiple products for observability - LGTM stack (Loki for logs, Grafana for visualization, Tempo for traces, and Mimir for metrics). You need to configure and maintain multiple sub-products for a full-stack observability setup.

While grafana stack is great, OneUptime has all of these in one platform and makes it really simple to use.

We also are built natively on OpenTelmetry, use clickhouse for logs / metrics / traces storage - so queries are really fast.

Postgres for tx data. Clickhouse for storing logs / traces / metrics.

Oh yes! there's no native Jira integration so far - but we have some customers who already integrate oneuptime with Jira. They integrate Jira through workflow webhooks in OneUptime - so when an issue is created in Jira, incident is created in OneUptime and all Status Page subscribers are notified.

I believe this is what you're looking for: https://oneuptime.com/product/workflows

OneUptime is 100% open source, and always will be. It's a mono-repo and backend is divided into few services.

This is very interesting. Hope this catches on.

Homelabbers like me have a docker swarm cluster / k8s cluster so this def helps!

Costs. We actually did this for EU - looking to replicate same for the US.

https://blog.oneuptime.com/moving-from-aws-to-bare-metal/

This is amazing. We'll reach out to HEY founders to see what their experience is.

Thank you for all your recommendations. Latency is not a concern because we will use that rack to store logs, metics and other telemetry data for our customers.

I believe major concern is power + bandwidth and good support because we wont be able to drive / fly there at moments notice.

Thank you for the feedback. We will potentially look into iterating on the interview process whcih will include not contributing to any of our projects if devs feel this way.

PS: About code deletion, we have updated docs here: https://github.com/OneUptime/interview/blob/master/software-...

PS2: We're a tiny team. We're profitable and 100% bootstrapped.

Honest reason for doing this: A lot of candidates would hopefully appreciate the work they have put in to the interview does not go to waste and is part of some FOSS project out there.

We have seen endless take home tasks from other companies that you spend few days to work on and that goes to waste.

We also give them an option to delete all the code they have written at the end of the interview.

Here is my portfolio:

50% into Index Funds.

40% into Real Estate (or Real Estate Funds)

10% into Bitcoin (Bitcoin ONLY, not crypto).

OneUptime | Staff Software Engineer or Full Stack Developer | 220K-250K | Remote.

OneUptime is an open-source observability platform. Think open-source DataDog.

You will be working on these technologies when you’re working with us.

Typescript, ReactJS, NodeJS, Docker, Kubernetes, GitLab CI, Jenkins, Tests with Mocha, Chai, Puppeteer, Jest etc. Postgres, Redis, Clickhouse

Apply here: https://github.com/OneUptime/interview