Skip to content

Promitor Scraper Agent has encountered an unexpected error #2017

Answered by tomkerkhove
kad-meedel asked this question in Q&A
Discussion options

You must be logged in to vote

Given you are upgrading to a new major version, you should align your configuration with the introduced breaking changes as announced in https://blog.tomkerkhove.be/2021/01/06/announcing-promitor-2-0-bringing-azure-monitor-metrics-where-you-need-them/

This migration guide should be able to help you: https://docs.promitor.io/walkthrough/migrate-from-1.x-to-2.x

The problem you are having (at least) is that you are not defining any metric sinks.

So what I would suggest is:

  1. Migrate to latest Promitor version
  2. Follow migration guide to align
  3. Re-deploy

Feel free to let me know how it goes

Replies: 8 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@kad-meedel
Comment options

@tomkerkhove
Comment options

Answer selected by kad-meedel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
bug Something isn't working
2 participants
Converted from issue

This discussion was converted from issue #2014 on April 26, 2022 08:32.