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

Emitting custom metrics from hook functions #161

Closed
1 of 4 tasks
hassy opened this issue Sep 3, 2016 · 4 comments
Closed
1 of 4 tasks

Emitting custom metrics from hook functions #161

hassy opened this issue Sep 3, 2016 · 4 comments

Comments

@hassy
Copy link
Member

hassy commented Sep 3, 2016

It's possible to add custom stats to Artillery's reports from hook functions as described here: #160 (comment)

The ability to do this is massively useful but the current code is only a proof-of-concept and needs to be rewritten.

  • Logging histograms should be possible (already implemented)
  • Logging counters should be possible
  • It should be possible to merge custom metrics from several Artillery processes (when running on multiple cores / machines)
  • It should be possible to annotate custom metrics with information for the graphical (HTML) reports
@kieranbop
Copy link

Hello @hassy , I've tried some of these custom hook functions to ensure pre-authentication occurs and log errors etc but I was wondering if it is possible to breakdown the status codes being returned for each uri and report them in the custom stats?
My flow does 5 gets currently, but I want visibility of where my failure occurs without scrolling through DEBUG mode trying to figure it out.
Could it just be as simple as anything other than 200 , add a counter for each particular get call for each particular code?

@hassy
Copy link
Member Author

hassy commented Sep 27, 2017

Not possible at the moment @kieranbop, custom counters haven't been implemented yet.

@hassy
Copy link
Member Author

hassy commented Apr 26, 2021

https://artillery.io/docs/guides/guides/extending.html#Tracking-custom-metrics

@hassy hassy closed this as completed Apr 26, 2021
@eliezercazares
Copy link

Broken link my dude.
I see everywhere the code for customStats but I am not able to figure out how to add big strings to it. (A json representing the "top" unix terminal command output).

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

No branches or pull requests

3 participants