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

Creating Custom Output Extensions #41

Closed
Expecho opened this issue Feb 2, 2017 · 5 comments
Closed

Creating Custom Output Extensions #41

Expecho opened this issue Feb 2, 2017 · 5 comments
Assignees

Comments

@Expecho
Copy link
Contributor

Expecho commented Feb 2, 2017

How does one create a custom output. I've take the code form the standard output sink but when hooking things up it does not work (as in, no breakpoint are hit, no error messages appear.

I think I need more info about what to put into the extensions configuration of the config file.

@karolz-ms karolz-ms self-assigned this Feb 2, 2017
@karolz-ms
Copy link
Collaborator

Good point, we should probably update the docs.

In the meantime please take a look at diagnostic pipeline factory tests, in particular the test called CanOverrideDefaultPipelineItems. Basically, you need to create a factory for your output, then point EventFlow to that factory via an element in the extensions section of the configuration. In case of a custom output the "category" must be set to "outputFactory", "type" to whatever you want the output to be referred as (e.g. "myAwesomeOutput") and the "qualifiedTypeName" needs to be set to a string that allows EventFlow to instantiate the factory via Type.GetType(typeName)

This of course assumes you want to use the configuration. Nothing prevents you from bypassing DiagnosticPipelineFactory altogether and instantiating a DiagnosticPipeline directly. See diagnostic pipeline tests for examples. For testing the output that is probably preferable.

@Expecho
Copy link
Contributor Author

Expecho commented Feb 3, 2017

Thanks, I got it working now! Do you guys have plans for additional Input/output items that will be provided out of the box? For example, I see there is a TableStorage output that is not yet included in the latest NuGet package.

@karolz-ms
Copy link
Collaborator

We are planning to add an input for manifest-based ETW providers very soon. Other than that we have a long backlog but priorities are continuously shifting :-)

What input or outputs would you like to see?

@Expecho
Copy link
Contributor Author

Expecho commented Feb 6, 2017

Well, I was thinking about azure blob storage or azure data lake so we can analyze them using for example Azure DataLake analytics

@karolz-ms
Copy link
Collaborator

Makes sense. Can't make any promises at the moment, but we have heard from several people about rolling log files, BLOB storage and DataLake, so these are definitively on the radar.

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

No branches or pull requests

2 participants