Skip to content
New issue

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

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

Already on GitHub? # to your account

[servicegraphconnector] Add flush interval config #27879

Merged
merged 6 commits into from
Oct 24, 2023

Conversation

mapno
Copy link
Contributor

@mapno mapno commented Oct 20, 2023

Description: Add a config option to periodically flush metrics, instead of flushing on every push.

Link to tracking Issue: #27679

Testing: Added tests that verify metrics are flushed asynchronously

Documentation: Documentation added to config.go

@mapno mapno requested a review from jpkrohling as a code owner October 20, 2023 09:12
@mapno mapno requested a review from a team October 20, 2023 09:12
@github-actions github-actions bot added the processor/servicegraph Service graph processor label Oct 20, 2023

// Metrics are not immediately flushed
assert.Len(t, metricsExporter.md, 0)
time.Sleep(time.Second * 5)
Copy link
Member

Choose a reason for hiding this comment

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

Can you do a smaller flush interval for this test and use assert. Eventually here? Otherwise, the test will take at least 5 seconds to run. Seen individually, it's not a huge problem, but on the bigger context, it might cause our CI to take longer and longer :-/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed!

@jpkrohling jpkrohling changed the title Servicegraph flush interval [servicegraphconnector] Add flush interval config Oct 24, 2023
@jpkrohling jpkrohling merged commit 3a27029 into open-telemetry:main Oct 24, 2023
@github-actions github-actions bot added this to the next release milestone Oct 24, 2023
sigilioso pushed a commit to carlossscastro/opentelemetry-collector-contrib that referenced this pull request Oct 27, 2023
**Description:** Add a config option to periodically flush metrics,
instead of flushing on every push.

**Link to tracking Issue:** <Issue number if applicable> open-telemetry#27679

**Testing:** <Describe what testing was performed and which tests were
added.> Added tests that verify metrics are flushed asynchronously

**Documentation:** <Describe the documentation added.> Documentation
added to `config.go`

---------

Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de>
jmsnll pushed a commit to jmsnll/opentelemetry-collector-contrib that referenced this pull request Nov 12, 2023
**Description:** Add a config option to periodically flush metrics,
instead of flushing on every push.

**Link to tracking Issue:** <Issue number if applicable> open-telemetry#27679

**Testing:** <Describe what testing was performed and which tests were
added.> Added tests that verify metrics are flushed asynchronously

**Documentation:** <Describe the documentation added.> Documentation
added to `config.go`

---------

Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de>
@mapno mapno deleted the servicegraph-flush-interval branch November 20, 2023 14:59
bogdandrutu pushed a commit that referenced this pull request Jan 10, 2024
…opy configuration README (#29919)

**Documentation:** <Describe the documentation added.>
#27879 recently added a new configuration option to the `servicegraph`
components called `metrics_flush_interval`. I noticed this wasn't
documented for either component, and the `connector/servicegraph` README
doesn't include a configuration section. Since the connector is just a
wrapper of the processor at this point, I cleaned up the processor's
configuration section and copied it to the connector, adding an entry
for the new `metrics_flush_interval` option.
cparkins pushed a commit to AmadeusITGroup/opentelemetry-collector-contrib that referenced this pull request Jan 10, 2024
…opy configuration README (open-telemetry#29919)

**Documentation:** <Describe the documentation added.>
open-telemetry#27879 recently added a new configuration option to the `servicegraph`
components called `metrics_flush_interval`. I noticed this wasn't
documented for either component, and the `connector/servicegraph` README
doesn't include a configuration section. Since the connector is just a
wrapper of the processor at this point, I cleaned up the processor's
configuration section and copied it to the connector, adding an entry
for the new `metrics_flush_interval` option.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
processor/servicegraph Service graph processor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants