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

Pause Elastic APM monitoring. #575

Closed
umarriqbal opened this issue Aug 28, 2019 · 3 comments
Closed

Pause Elastic APM monitoring. #575

umarriqbal opened this issue Aug 28, 2019 · 3 comments

Comments

@umarriqbal
Copy link

umarriqbal commented Aug 28, 2019

I don't think this is already a feature or if there is a viable workaround around it.
I'm looking to dynamically pause/resume APM monitoring.
I'm using:

Python 3.5
Flask 1.0.2
Elastic APM 6.6.2

Detail:
I'm trying to monitor logs or transactions only when a particular type/URL of request comes in. One way that I can achieve that is to reject/sanitise my transactions but that still includes the overhead of monitoring by Elastic APM. I want to get rid of the overhead completely since I deal in super realtime responses.

/edit:

Spec

To align with the other agents and to provide greater flexibility, we're introducing two new config options: enabled and recording, while deprecating active.

Here's the expected behavior as described in elastic/apm#92 (comment):

  • enabled - Should behave identically to active, which in turn should be deprecated (this is essentially a rename to get a more meaningful name)
  • recording - Should default to true. Setting to false will completely disable the recording and sending of data (transactions, spans, errors, and metrics). It must be possible to toggle recording dynamically, either locally or via remote config. Setting recording to false will therefore not disable remote config polling, config file watching, etc.
@beniwohli
Copy link
Contributor

Hi @umarriqbal

While such an option does not currently exist, we do have it on our roadmap: elastic/apm#92 (comment). I haven't had a chance to open an implementation issue in this repo. If it's alright with you, I'll "declare" this issue the implementation issue and will add a short spec to your message.

@umarriqbal
Copy link
Author

Hi, @beniwohli. That'll be great.

@basepi
Copy link
Contributor

basepi commented Jul 9, 2020

This was introduced in #790 -- RECORDING is the config that you're looking for.

@basepi basepi closed this as completed Jul 9, 2020
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

No branches or pull requests

3 participants