Skip to content

Conversation

OleksiienkoMykyta
Copy link
Contributor

@OleksiienkoMykyta OleksiienkoMykyta commented Jul 24, 2024

The are 2 new columns in Cassandra:
system_traces.sessions.coordinator_port
system_traces.events.source_port
They should be exposed to the user to have the opportunity to check trace info.
https://datastax-oss.atlassian.net/browse/PYTHON-1229

Notice: This fields exists in Cassandra V3 but always equals null, only from Cassandra v4 we can get the ports.
Also, I found some columns from system_traces.sessions that didn`t exposed for user as well yet (client | command | parameters | request | started_at)

iter := t.session.control.query(`SELECT coordinator, duration
FROM system_traces.sessions
WHERE session_id = ?`, traceId)
iter := t.session.control.query(`SELECT coordinator, duration, coordinator_port

Choose a reason for hiding this comment

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

We can switch places of duration and coordinator_port fields a little bit:

SELECT coordinator, coordinator_port, duration

It will be more logical to display info about coordinator node this way

Comment on lines +2145 to +2147
iter = t.session.control.query(`SELECT event_id, activity, source, source_elapsed, source_port, thread
FROM system_traces.events
WHERE session_id = ?`, traceId)

Choose a reason for hiding this comment

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

The same is true here. We can change the place of source_port to:

SELECT event_id, activity, source, source_port, source_elapsed, thread

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.

2 participants