rfarley3 / Kibana

Kibana 4 configuration index interaction (.kibana index control, import and export of config, dashboards, visualizations, searches)
MIT License
18 stars 15 forks source link

Similar project #15

Open jpparis-orange opened 7 years ago

jpparis-orange commented 7 years ago

I started the following project a couple of months ago: https://github.com/jpparis-orange/kibtool. Although I searched github before starting my project, I stumbled upon rfarley3/Kibana right now.

As both projects seem to share common goals, would it be a good way to "merge" the efforts?

rfarley3 commented 7 years ago

My project problem space is:

I see that you focus on migrating one .kibana to another. But you also have an export (to file) option, which would probably fit my needs. Can that exported file be imported using the Kibana UI (in settings > objects)? Can you read the Kibana UI's export?

I'd prefer to see a single Kibana CLI tool out there, so I'd be happy to help unify tools. What features in dotkibana are complimentary to kibtool? Are there any issues outstanding/closed in this repo that you have already/yet fixed in yours? Also, have you seen this other kibtool.

jpparis-orange commented 7 years ago

With (my) kibtool, your first problem is addressed, even if when you load a kibtool saved file, you'll get an error (I save index-pattern that are can't be loaded by Kibana). The opposite works fine.

About the refresh problem, I had the same question from a colleague last week: I do think it's a needed feature (in the same CLI or in another one, I don't know at the moment...)

I have found the other kibtool seems, but it seems to be untouched since 2 years...

jpparis-orange commented 7 years ago

I had a closer look at your code: it' more pythonic that mine (indent, naming, PyPI installation for example). In mine, I have (some) unit tests and integration tests.

I have read pending issues, and it help me understood your approach to index patterns. It seems to be better than mine.

The basis of export is like mine: compute all dependencies from a dashboard so that it is exported as a consistent set of objects.