Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/jitsu/issues.md or /mcp/jitsu/issues.json, or Pod over MCP.

Reported issues for Jitsu

Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to Jitsu.

Most discussed

s2s/events endpoint not documented

Problem

There is s2s/events endpoint to enqueue events in batch but it is not mentioned in docs. Why?

Solution

Add docs for this endpoint.

Also I'd like to say thank you for all your hard work on this project 🙂

Read the thread · 2022-01-11 · closed · external user · 3 comments

Who to contact for security issues

Hey there!

I belong to an open source security research community, and a member (@sudheendra17) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instructio

Read the thread · 2021-10-17 · closed · external user · 1 comment

Generate API Connectors documentation based on the Catalog

Problem

At present we don't have documentation about how to configure access or how to gather configuration parameters that Jitsu uses in API connectors synchronization. It is very important to provide clear step-by-step documentation about all pre-requirements to users for making their product experience better.

Solution

We should generate documentation based on the Catalog. Every API Connector (both native and Singer) should have a documentation node that contains JSX format

Read the thread · 2021-06-10 · closed · external user · 0 comments

OAuth support (for connectors)

Problem

Obtaining secrets & tokens for connectors is a pretty time-consuming task. The user should click-through pretty sophisticated interfaces. We need to implement OAuth where it's possible.

Solution

Some connectors might have oauth enabled. OAuth secrets should be configurable for those connectors (some connectors can share the secrets).

UI

TODO

Backend

Read the thread · 2021-05-27 · closed · outside contributor · 0 comments

Telemetry improvements

Problem

At present Jitsu tracks, the only server starts/stops events and events from JS/API. We should improve telemetry for understanding how users use our product. There should be additional telemetry in the jitsucom/server as well as in jitsucom/configurarator frontend. We should understand:

Read the thread · 2021-04-06 · closed · external user · 0 comments

Amplitude destination

Support Amplitude as a destination. See API

Read the thread · 2021-03-11 · closed · outside contributor · 0 comments

Support GA measurement protocol as a destination

Some users want to send data to GA instead of DWH

This issue is about research if this feature will work nicely along with our data infrastructure. Here's a link to GA protocol The preliminary design is:

{
   "tid": 1,
   "sid": 2
   ....
}

The adapted should treat property as [measurement protocol parameter](https://dev

Read the thread · 2020-11-16 · closed · outside contributor · 1 comment

Privacy: Run self-hosted tracker without cookie

First: This looks like a very promising project! Thank you very much for your work! Once the Clickhouse integration is finished, this could replace our own hacky solution for tracking events.

But there is one caveat and this is the GDPR and the cookie regulations we see here in Europe. Using cookies for tracking purposes requires us to inform the user and collect an opt-in (which they most likely won't do anyways... ).

Could you imagine to add a cookie-less mode for the tracking script?

Read the thread · 2020-08-12 · closed · external user · 4 comments

Most recent

Generate API and docs with Open API

Problem

At the moment Jitsu has two servers with JSON-based APIs:

Both of them have manual API documentation which are not always in sync with actual implementation. [1]

The other problem that is related to APIs is the way how Jitsu UI communicates with Configurator. If UI needs to update any of the core entities (destination, api_key, source etc), it updates the whole list of entities which is not efficient and exposes UI to change conflicts. [2]

Read the thread · 2021-06-14 · closed · external user · 0 comments

The remaining reports are on the project's issue tracker.