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.

Sign up for GitHub

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

Jump to bottom

Behaviour of proccon after a skydive restart with data loaded from Elasticsearch #3

Open
adrianlzt opened this issue Jan 11, 2021 · 0 comments
Open

Behaviour of proccon after a skydive restart with data loaded from Elasticsearch #3

adrianlzt opened this issue Jan 11, 2021 · 0 comments
Labels
proccon Related with the topology probe to receive connection/ports info from Telegraf

Comments

@adrianlzt
Copy link

When skydive is started and it have data in Elasticsearch, does the internal indexes used by proccon initialized with the info stored in Elasticsearch?

Or does the probe start from sratch, without information about connections and ports of procs?
@adrianlzt adrianlzt added the proccon Related with the topology probe to receive connection/ports info from Telegraf label Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
proccon Related with the topology probe to receive connection/ports info from Telegraf
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adrianlzt