Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include created timestamp in protobuf output format #1182

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

mantuu
Copy link

@mantuu mantuu commented Nov 2, 2024

Hi, this is actually needed for the feature "created-timestamp-zero-ingestion", which work with the protobuf-protocoll.

this(false);
}

public PrometheusProtobufWriter(boolean writeCreatedTimestamps) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to avoid boolean params - let's use a builder instread

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this even be configurable? It makes sense to make timestamps configurable in text format, because in text format timestamps end up as extra time series which cause extra load on the Prometheus server.

However, in protobuf format time stamps do not cause extra cost, so we could just enable them always, right?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fstab This makes sense. It should make almost no difference in protobuf. So I am thinking of removing the boolean-constructor (@zeitlinger) and make protobuf always include the created-timestamp (as long it is not null).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants