jmeter-prometheus-plugin

jmeter-prometheus-plugin copied to clipboard

I tried putting 30 sec or more to the prometheus.delay property, but as soon as Jmeter test stop, metrics http server is down immediately and Prometheus scrapper loses the data. how to resolve this?

I would suggest to add a empty/idle 'virtuale user'/thread at the end of your test plan.

Please consider that the http server goes down as soon the test plan ends since it is spawned within the jmeter java process

Luca

Il mer 21 ago 2019, 01:49 jyoprakashJP [email protected] ha scritto:

I tried putting 30 sec or more to the prometheus.delay property, but as soon as Jmeter test stop, metrics http server is down immediately and Prometheus scrapper loses the data. how to resolve this?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/johrstrom/jmeter-prometheus-plugin/issues/58?email_source=notifications&email_token=AB2WL4B3ZESLHVGAIJDGMH3QFQVDHA5CNFSM4IN2TU62YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HGJ6S2A, or mute the thread https://github.com/notifications/unsubscribe-auth/AB2WL4EHY2MOVSS7IAVXJXTQFQVDHANCNFSM4IN2TU6Q .

yes, I already tried with teardown thread group, and it works that way

Looking at the Javadocs, it appears my understanding of delay is not what I had thought. It looks like the server will probably just stop immediately because it likely does not have any traffic.

Marking this as a bug because as a user, you've expected it to behave in a way that it does not, and I agree that that is the behaviour that should happen.

It seems like there's a workaround with is good, but, nonetheless, this feature seems to be broken.

Hello, were you able to fix the bug? If not, could you please suggest a workaround?

I feel like #116 should have fixed this. Can you try an updated version? Looks like that change made it into 0.6.1.