You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the resolution to issue #14, the idea was floated that instead of just supporting Authorization headers, the exporter should support all types of headers for calling the Prometheus API. So, as opposed to key-value pairs of Prometheus instance identifiers and Authorization header values, the input file would consist of identifiers mapping to many header key-value pairs.
We decided that this would not be implemented at this moment, however, if anyone were to require it we would reconsider. Please comment below if this is something you require!
The text was updated successfully, but these errors were encountered:
During the resolution to issue #14, the idea was floated that instead of just supporting Authorization headers, the exporter should support all types of headers for calling the Prometheus API. So, as opposed to key-value pairs of Prometheus instance identifiers and Authorization header values, the input file would consist of identifiers mapping to many header key-value pairs.
Example:
We decided that this would not be implemented at this moment, however, if anyone were to require it we would reconsider. Please comment below if this is something you require!
The text was updated successfully, but these errors were encountered: