The project took about 3 days.
This seems to me to provide a (semi-roundabout) answer to your question. Let's say you work for a particular employer for five years. That's about 1,800 days, minus weekends and some vacation time. Let's pretend that the employer gives you European-style vacations and call that a nice, round 1,200 days actually worked. The exact number is going to be different between countries and possibly between employment forms, but globally, that seems a reasonable guesstimate.
The project you mention would then have taken all of 0.25% of your time working for this employer.
Sure, it may have been interesting or challenging, but remember that your résumé is a sales pitch. Lots of engineer types in particular tend to forget about that. The purpose of your résumé is to make the employer interested enough in you for you to get your foot in the door for an interview. The purpose is not to list everything you ever worked on.
So, you want to paint with broad strokes, but at the same time be specific. Technologies. Numbers. How what you did helped your employer's bottom line. Describing something that you spent a fraction of a percent of the time you worked for the employer doing, then, seems counterproductive. If my math is right and this is the median length of a project of yours, your résumé will list a few hundred projects of that size or larger. No prospective employer is likely to read through such a list. They would put your résumé in the "to be read later" pile (also known as the Round Archive).
Hence, unless the project actually adds something specific to your experience which you believe a future employer might be interested in, I would suggest that you leave out the specific mention of it. It was a minor project in the grand scheme of things and it didn't turn out to provide any significant benefit to your employer; in fact, since it didn't work out and was reverted, it was essentially wasted money for them. (Not to say they didn't learn from the experience, but it didn't improve their business case toward their customers.) If you learned additional technologies or something like that through it, you may want to mention those as "also worked with" or something similar. It might make a good conversation piece during an interview if the interviewer asks "what did you do that used Kibana?", but I wouldn't consider the failed, relatively small assignment to be something that actively sells you to an employer.
However, as I also mentioned in a comment to the question, this type of experience sounds like a good answer to the classic "please tell me about a particular failure in your work" type of question: you were asked to do something, did it, it worked, but in the end it didn't work out for reasons unrelated to your work performance. There is a lot of learning potential from an experience like that; show the prospective employer that you learned from it. But my suggestion would definitely be to not make the specific mention until you've got your foot in the prospective employer's door by being there for an interview.