This repository was archived by the owner on Nov 17, 2017. It is now read-only.
Open
Conversation
|
Using this, would I be able to create a field format which translates numbers such as "4740" and "4730" into "4740 - account locked out" and "4730 - account unlocked" (windows EventID's ;) for a field names EventID ? or is that too specific. In my use case i could just harcode the list of EventID's to replace. |
Author
|
@KlavsKlavsen that is exactly what you could do with a field formatter. You could hardcode the list of ids (or even create a server interface to retrieve it from other documents) and then let the field formatter look up the id in the map you have and append it. |
|
Looking forward to you merging this - now you have commit access ;) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @spalger,
this branch has a first draft of a components subgenerator in it. It has a field format subgenerator, that can be called with
yo kibana-plugin:field-formatand will generate new files. Also it has the auto detecting feature in the main generator for field formats right now.Every feedback highly welcome. If this is a base one could work of, we could create several subgenerators for the different components, link them up in the main generator and - imo - throw away the "old" sample components in the main generator.