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

Add varnishlogbeat and varnishstatbeat #4353

Merged
merged 1 commit into from
May 19, 2017
Merged

Add varnishlogbeat and varnishstatbeat #4353

merged 1 commit into from
May 19, 2017

Conversation

phenomenes
Copy link
Contributor

No description provided.

@karmi
Copy link

karmi commented May 18, 2017

Hi @phenomenes, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

@elasticmachine
Copy link
Collaborator

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run.

1 similar comment
@elasticmachine
Copy link
Collaborator

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run.

@phenomenes
Copy link
Contributor Author

@karmi email address updated

@elasticmachine
Copy link
Collaborator

Can one of the admins verify this patch?

@ruflin
Copy link
Member

ruflin commented May 19, 2017

@phenomenes Thanks a lot for creating these two beats.

For varnishbeat it sounds to me like it would fit perfectly into a varnish metricbeat module (which we don't have yet).

For the varnishlogbeat it sounds like it could fit into filebeat. I was recently working on filebeat an restructuring it to allow also other types of prospectors. One first example here is the redis slowlog prospector: #4180 Perhaps it could also be part of filebeat in the future? Does the varnishlog have a state?

@phenomenes
Copy link
Contributor Author

@ruflin what do you mean by state?

@ruflin
Copy link
Member

ruflin commented May 19, 2017

By state I mean if it keeps track somehow on until where it was reading. Like the offset in filebeat with the registry. Or how do you decide where to start reading the log after restarting the beat?

@ruflin ruflin merged commit 4c24665 into elastic:master May 19, 2017
@phenomenes phenomenes deleted the varnish-beats branch May 19, 2017 11:20
@phenomenes
Copy link
Contributor Author

It doesn't maintain state, is event based.

About varnishstats I haven't fully read metricbeat code yet but I think it could fit.

@ruflin
Copy link
Member

ruflin commented May 19, 2017

Means if you restart, you just start to fetch the events that are flowing from this point in time and not from the past.

About the metricbeat module: It would be really great to have a contribution for a varnish module. Here is the dev guide: https://www.elastic.co/guide/en/beats/metricbeat/current/creating-metricsets.html In case you are interested, just ping me if I can help somehow ;-)

@phenomenes
Copy link
Contributor Author

that's exactly what it does, so yes, it maintains state.

cool, I don't have much time right now but I'll have a look as soon as I'm free.

@ruflin
Copy link
Member

ruflin commented May 22, 2017

@phenomenes About the state: I need to have a closer look into varnishlogbeat to see what the state structure is.

@phenomenes
Copy link
Contributor Author

To clarify, varnishlogbeat does not maintain state. It will always read starting from the last record, this is handled automatically by Varnish.

@ruflin
Copy link
Member

ruflin commented May 23, 2017

Interesting. So if you reconnect it knows where you left off.

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

Successfully merging this pull request may close these issues.

5 participants