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

[receiver/mysql] Add mysql.connection.count metric #14736

Conversation

sumo-drosiek
Copy link
Member

Description:

add mysql.connection.count metric

Link to tracking Issue:

#14138

Testing:

unit tests

Documentation:

metadata.yaml

@sumo-drosiek sumo-drosiek requested a review from a team October 6, 2022 06:21
@djaglowski djaglowski changed the title feat(mysqlreceiver): add mysql.connection.count metric [receiver/mysql] Add mysql.connection.count metric Oct 6, 2022
@sumo-drosiek sumo-drosiek force-pushed the drosiek-mysql-connection-count branch from d749642 to f627dc2 Compare October 7, 2022 06:10
@@ -283,6 +283,15 @@ metrics:
monotonic: false
aggregation: cumulative
attributes: [threads]
mysql.connection.count:
enabled: true
Copy link
Member

Choose a reason for hiding this comment

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

Do we want to enable this? It is always hard to disable later, and I feel that we almost enable everything.

Copy link
Member

Choose a reason for hiding this comment

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

The comment is not to block this PR, but to ensure that someone starts thinking about this and makes a proposal.

Copy link
Member

Choose a reason for hiding this comment

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

So far, my heuristics for disabling metrics by default have been for things like:

  • If it creates high cardinality of resources and/or data points
  • If there is a notable expected performance impact
  • If there is unusual configuration required (on monitored system or collector)

In general, I think of metrics as otherwise being pretty cheap, but I agree we should probably establish some kind of limitations based on how valuable a metric is vs others.

Copy link
Member Author

Choose a reason for hiding this comment

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

Should it go as enabled, or should I disable it and we can enable them in separate PR eventually?

Copy link
Member Author

Choose a reason for hiding this comment

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

@djaglowski @bogdandrutu
Disabled metric by default and rebased the branch

@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added Stale and removed Stale labels Oct 28, 2022
Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
@sumo-drosiek sumo-drosiek force-pushed the drosiek-mysql-connection-count branch from 8dacef5 to 33bc97d Compare November 2, 2022 10:40
@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Nov 17, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2022

Closed as inactive. Feel free to reopen if this PR is still being worked on.

@github-actions github-actions bot closed this Dec 2, 2022
@sumo-drosiek
Copy link
Member Author

@djaglowski @bogdandrutu can we reopen and merge this PR?

@djaglowski
Copy link
Member

@sumo-drosiek I cannot reopen the PR, but will happily accept a new one. Looks like all concerns were addressed here and this was just forgotten about.

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

Successfully merging this pull request may close these issues.

3 participants